On Jan 29, 2008, at 3:46 AM, Gordon Sim wrote:
Rupert Smith wrote:On 28/01/2008, Rajith Attapattu <[EMAIL PROTECTED]> wrote:Just for my understanding, What is the difference between M2.1 and M2.1.1 ? Which branch are we planning to use for the next release of M2.x?Rajith, If you wanted to apply a bug-fix to a piece of software inproduction, would you not want to apply it to the exact source that was used to build the production system, so as to be very careful to fix just that bug without risking introducing bugs, or simply incompatibilities, that may have been created as the source evolved onwards from the point at which theproduction system was cut?Of course. However I think the question is a good one. As we have in effect two streams of work in the project, lets call them 0-8/0-9 and 0-10 to avoid confusion, which branch holds the ongoing development for the 0-8/0-9 stream, and will be used for the next release of that stream? I believe from Aidan's response that the answer is M2.1.I'm don't think it is possible to have an open branch for every 'production system'. The only way to ensure that only the desired fixes are made to a particular deployed system is to start from the exact source and apply locally relevant patches, then rebuild from the patched code.I think we would benefit from a clear policy on what we keep branches for and how each open branch is to be used.
+1Other projects have policy on release numbering [1] that tie into processes for release management [2].
Craig [1] http://openjpa.apache.org/openjpareleasepolicy.html [2] http://openjpa.apache.org/releasing-openjpa.html Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
