Master Ticket/Task List: REVIEW REQUESTED

[John Poelstra]

I sat down with Jesse after going through all the tickets for Fedora 12 
to capture ALL the tickets that we create for each release.

The idea here is that we can automate this process for each release.  To 
do that I wanted to make sure I captured all of the tickets we need to 
create for each public milestone (Alpha, Beta, Final)

We captured all of this on:
https://fedoraproject.org/wiki/Release_Engineering_Release_Tickets

Please review this wiki page and correct/add as appropriate.  I'd love 
feedback before Friday so that I can take the next step which is to 
create all these tickets.

Thanks,
John

[Bill Nottingham]

John Poelstra (poelstra(a)redhat.com) said: 
>  I sat down with Jesse after going through all the tickets for Fedora
> 12 
>  to capture ALL the tickets that we create for each release.
>  
>  The idea here is that we can automate this process for each release.  To 
>  do that I wanted to make sure I captured all of the tickets we need to 
>  create for each public milestone (Alpha, Beta, Final)
>  
>  We captured all of this on:
>  https://fedoraproject.org/wiki/Release_Engineering_Release_Tickets
>  
>  Please review this wiki page and correct/add as appropriate.  I'd love 
>  feedback before Friday so that I can take the next step which is to 
>  create all these tickets. 
At the same time rawhide is branched, might want to explicitly state
that there is koji work to be done there too to:

- repoint rawhide
- set up the build repos for the next release
- set up the updates repos for the current release

Also, somewhere there needs to be a 'create signing key' event, unless
we go to a single key for all releases.

Coordinating artwork usually happens closer to beta.

Bill

[John Poelstra]

Bill Nottingham said the following on 12/08/2009 12:50 PM Pacific Time:
>  John Poelstra (poelstra(a)redhat.com) said: 
> > I sat down with Jesse after going through all the tickets for Fedora 12 
> > to capture ALL the tickets that we create for each release.
> >
> > The idea here is that we can automate this process for each release.  To 
> > do that I wanted to make sure I captured all of the tickets we need to 
> > create for each public milestone (Alpha, Beta, Final)
> >
> > We captured all of this on:
> > https://fedoraproject.org/wiki/Release_Engineering_Release_Tickets
> >
> > Please review this wiki page and correct/add as appropriate.  I'd love 
> > feedback before Friday so that I can take the next step which is to 
> > create all these tickets.
>  
>  At the same time rawhide is branched, might want to explicitly state
>  that there is koji work to be done there too to:
>  
>  - repoint rawhide 
Can you be more specific?  "repoint rawhide" at what?

>  - set up the build repos for the next release
>  - set up the updates repos for the current release
>  
>  Also, somewhere there needs to be a 'create signing key' event, unless
>  we go to a single key for all releases.
>  
>  Coordinating artwork usually happens closer to beta.
>  
>  Bill 
Thanks Bill.

Anyone against me adding three more tickets to the list for the tasks 
Bill listed?

John

[Bill Nottingham]

John Poelstra (poelstra(a)redhat.com) said: 
>  >>Please review this wiki page and correct/add as appropriate.
>  >>I'd love feedback before Friday so that I can take the next step
>  >>which is to create all these tickets.
>  >
>  >At the same time rawhide is branched, might want to explicitly state
>  >that there is koji work to be done there too to:
>  >
>  >- repoint rawhide
>  
>  Can you be more specific?  "repoint rawhide" at what? 
The rawhide mash configs point at 'dist-rawhide'. dist-rawhide is
(essentially) a virtual tag in koji that points to, say, dist-f13.
When we branch, we need to set up dist-f14, dist-f14-build, etc.
and point dist-rawhide at dist-f14.

Bill

[Jesse Keating]

On Tue, 2009-12-08 at 13:33 -0500, Bill Nottingham wrote:
>  The rawhide mash configs point at 'dist-rawhide'.
> dist-rawhide is
>  (essentially) a virtual tag in koji that points to, say, dist-f13.
>  When we branch, we need to set up dist-f14, dist-f14-build, etc.
>  and point dist-rawhide at dist-f14.  
Actually I plan to change that as we go forward with n-f-r, dist-rawhide
would be an actual target and the rawhide mash config can always point
at it, since we won't be freezing it.

-- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating

[Jesse Keating]

On Tue, 2009-12-08 at 13:27 -0500, John Poelstra wrote:
>  > - repoint rawhide
>  
>  Can you be more specific?  "repoint rawhide" at what?
>  
>  > - set up the build repos for the next release
>  > - set up the updates repos for the current release
>  > 
>  > Also, somewhere there needs to be a 'create signing key' event,
>  unless
>  > we go to a single key for all releases.
>  > 
>  > Coordinating artwork usually happens closer to beta.
>  > 
>  > Bill
>  
>  Thanks Bill.
>  
>  Anyone against me adding three more tickets to the list for the tasks 
>  Bill listed?  
I'd be more in favor of outlining the steps in a SOP wiki page, rather
than creating one ticket per step.  That would cause something of a
ticket explosion.

The good news is that we have a set of tickets for which to create the
SOP pages from (:

-- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating