[PUP-4308] puppet-agent 1.0.0 2015-04-01 Release Created: 2015/03/25  Updated: 2018/04/03  Resolved: 2015/04/17

Status: Closed
Project: Puppet
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: Kylo Ginsberg Assignee: Release Engineering
Resolution: Fixed Votes: 0
Labels: AIO
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Blocks
Relates
relates to PUP-4292 puppet 4.0.0 2015-04-01 Release Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
PUP-4309 Is the code ready for release? Sub-task Resolved Josh Cooper  
PUP-4310 Is there a JIRA ticket targeted at th... Sub-task Resolved  
PUP-4311 Is there a commit for every JIRA tick... Sub-task Resolved  
PUP-4312 Update version number in source Sub-task Closed Kylo Ginsberg  
PUP-4313 Merge master into stable Sub-task Resolved Kylo Ginsberg  
PUP-4314 Is the Jira tidy-up done for this rel... Sub-task Resolved  
PUP-4315 Prepare long form release notes and s... Sub-task Closed Eric Sorenson  
PUP-4316 Tag the release and create packages Sub-task Resolved Melissa Stone  
PUP-4317 Smoke test packages Sub-task Resolved  
PUP-4318 Go/no-go meeting (before 4pm) Sub-task Resolved Kylo Ginsberg  
PUP-4319 Push tag Sub-task Resolved Melissa Stone  
PUP-4320 Packages pushed Sub-task Resolved Melissa Stone  
PUP-4321 Docs pushed Sub-task Closed Nicholas Fagerlund  
PUP-4322 Send out announcements Sub-task Resolved Eric Sorenson  
PUP-4323 Close all resolved tickets in Jira Sub-task Closed Kylo Ginsberg  
Template:
Story Points: 3
Sprint: Client 2015-04-15, Client 2015-04-29

 Description   

puppet 1.0.0 2015-04-01 Release

When working through this ticket, add it to the board and then keep it in the Ready for Engineering column.
Move the subtasks to In Progress when you are working on them and Resolved when you have completed them.
In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items.

  • The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them.
  • Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward.
  • When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.


 Comments   
Comment by Kylo Ginsberg [ 2015/03/25 ]

This is the puppet-agent ticket, pup-4292 is the puppet ticket. Creating two to make sure we cover all steps but some steps may be dups and can just be closed on one side or the other.

Comment by Kenn Hussey [ 2015/04/15 ]

Michael Stahnke is this still in progress or can it be resolved now?

Comment by Melissa Stone [ 2015/04/16 ]

Kenn Hussey we might still be waiting for docs. I'd check with Nicholas Fagerlund, but I think we still have a few days until docs are completely ready and this ticket is done.

Generated at Wed Nov 13 11:43:30 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.