Branching for next version
res <[email protected]>
| Newsgroups | gmane.comp.graphics.crystalspace.devel |
|---|---|
| Message-ID | <[email protected]> |
On 31.07.2012 21:44, Philip Wyett wrote: > True about the age. I just manage releases the decision to branch and push out > 2.1 is a community decision. > > Peoples thoughts? Well, first some nitpicking: Classically, we used odd numbers for development/prereleases, and even numbers for actual releases. Practically that means that current trunk is CS 2.1, the next branch would be for 2.2. On whether we should branch: my gut feeling is “not yet”. It would probably help to choose some features we'd like to have in the next release and/or a schedule we can use to base a branching decision on. Philip, do I recall correctly that you suggested a regular schedule/interval for releases at some earlier time?... -f.r. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Crystal-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-develop
signature.asc
(application/pgp-signature, 262 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAYUjwACgkQNCTzcE/07exA7QCfYcA2UOrqHKF4FsMaRkuu5d3C eJcAn1O4bFrCModsjKLQeof3uu+kUjxO =i03u -----END PGP SIGNATURE-----