[sakai2-tcc] [maint] Maintenance Branches: Enhancement vs Bug Merges
csev
csev at umich.edu
Wed Jan 5 09:22:32 PST 2011
I can really go either way on this issue and J-F makes very good points.
I just sent my Sakai 2.9 plans around to the dev list and at some level, if the Sakai 2.9 work turns out nicely and Sakai 2.9 is seen as a real positive step in the viability of Sakai in the marketplace (which I hope happens), then we would be well served to hold the tasty bits for Sakai 2.9 to get folks to come forward.
Again - I am switching sides on this because I truly see both sides. I personally am happy either way.
/Chuck
On Jan 5, 2011, at 10:41 AM, Jean-Francois Leveque wrote:
> Unless we want to get back to 2.4 time when it was a bad idea to use
> official releases, I think we should concentrate on delivering
> maintenance releases of 2.7 first instead of just merging changes into
> the maintenance branch.
>
> 2.7.1 is 4 months old and there are currently 103 issues with a 2.7.2
> fix version and 2.7.x Status of Resolved or Closed.
>
> Before 2.7.2 is released and we're able to deal with the backlog of bug
> fixes, I think it's a bad idea to merge anything than bug fixes.
>
> - J-F
More information about the sakai2-tcc
mailing list