[spin-kickstarts] #30: Create Fedora 13 milestones

[fedora-badges]

#30: Create Fedora 13 milestones
----------------------------+-----------------------------------------------
 Reporter:  kanarip         |       Owner:  kanarip     
     Type:  task            |      Status:  new         
 Priority:  major           |   Milestone:  Fedora 12 GA
Component:  kickstart pool  |    Keywords:              
----------------------------+-----------------------------------------------
 Create the Fedora 13 milestones

[fedora-badges]

#30: Create Fedora 13 milestones
----------------------------+-----------------------------------------------
 Reporter:  kanarip         |        Owner:  kanarip     
     Type:  task            |       Status:  closed      
 Priority:  major           |    Milestone:  Fedora 12 GA
Component:  kickstart pool  |   Resolution:  wontfix     
 Keywords:                  |  
----------------------------+-----------------------------------------------
Changes (by bruno):

* status:  new => closed
  * resolution:  => wontfix

Comment:

F13 is over. Rather than use milestones in trac, Polestra has made a spins
 part of the schedule using taskjuggler.

[John Poelstra]

spin-kickstarts said the following on 07/09/2010 09:55 AM Pacific Time:
> #30: Create Fedora 13 milestones
> ----------------------------+-----------------------------------------------
>   Reporter:  kanarip         |        Owner:  kanarip
>       Type:  task            |       Status:  closed
>   Priority:  major           |    Milestone:  Fedora 12 GA
> Component:  kickstart pool  |   Resolution:  wontfix
>   Keywords:                  |
> ----------------------------+-----------------------------------------------
> Changes (by bruno):
> status:  new =>  closed
> resolution:  =>  wontfix
>
> Comment:
>
> F13 is over. Rather than use milestones in trac, Polestra has made a spins
>   part of the schedule using taskjuggler.

I'm not sure I'd write of trac so quickly.  Trac is useful for knowing 
who is working on a particular task and if it is done or not.  The 
schedule simply says when it is supposed to be done.

John

[Bruno Wolff III]

On Thu, Jul 15, 2010 at 19:15:37 -0700,
  John Poelstra  wrote:
> I'm not sure I'd write of trac so quickly.  Trac is useful for knowing 
> who is working on a particular task and if it is done or not.  The 
> schedule simply says when it is supposed to be done.

For the F14 schedule it seems likely that it will be mostly just me and
writing tickets for the schedule that all point to me seems to be just
extra work. If it looks like stuff on the schedule will start getting
split up, then I think trac becomes more useful.

We did reaffirm a few weeks ago that we still want to use trac for tasks, in
fact I got a few far out low priority tasks at the last meeting and you
have reminded me that I should record those in trac.