A little bit ago I created the v2.4_branch. At the moment,
this branch is for bugfixes and stabilization only.
Write and test your bugfixes on the v2.4_branch. If you think there's
anything controversial about your changes, talk about it on irc or the
mailing list before pushing it. Do *not* make like changes on master;
bugfixes from v2.4_branch will be made on master in due time by merging
(at least, that's the theory until we see how it goes).
The creation of the v2.4_branch means that new features can go on master
again, but I hope that for the time being people will concentrate on
2.4.
As discussed earlier
http://mid.gmane.org/[email protected]
we are going to try the "merging upwards" strategy for putting selected
new features in 2.4. If you are doing work on a small feature and think
it might be sensible to add it to 2.4, read the gitworkflows document
and/or talk to me about how to work in a way that will make this
easiest.
Jeff
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
