The target date is not a deadline of some sort. I've set it so that the 2.1
release shows up on Assembla before 2.2 :-)

Let's release when it is ready. So if you want to release earlier, then
let's talk about the tickets that should be postponed to 2.2 in order to
shorten the list for 2.1. I've tried to use the priority to mark those
tickets I think are a must for 2.1. In my opinion, all tickets that do not
have high or highest priority can be postponed to 2.2

Reinier

> -----Oorspronkelijk bericht-----
> Van: [email protected] [mailto:tracks-discuss-
> [email protected]] Namens Matt Rogers
> Verzonden: vrijdag 4 november 2011 19:57
> Aan: [email protected]
> Onderwerp: [Tracks-discuss] 2.1 Release Scheduling
> 
> Hi,
> 
> What does everybody think about moving up the Tracks 2.1 release to the
> middle of November and starting on Tracks 2.2 sooner? In Assembla, the
> target date is 12/31 but with the impending holidays, it doesn't make a
lot of
> sense to do that. Why don't we release earlier and start on Tracks 2.2
> sooner?
> 
> I have a feeling that most of us want to start on the rails 3 migration
sooner
> rather than later anyways. ;)
> 
> Thanks
> --
> Matt
> _______________________________________________
> Tracks-discuss mailing list
> [email protected]
> http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss

_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss

Reply via email to