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?
For me it makes sense to start with the Rails 3 migration soon. So +1
Btw. I'm asking me if it would be better to have a smaller scope for
each release, but release more often.
With a rather small team of developers, I think this would have several
advantage
- focused on a fewer numbers tickets
- a higher quality could be achived this way
- a individual release is managable, so easier to plan
- more feedback on new features
- more motivation to implement a ticket for the current release, as
result will be published sooner.
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
