On Fri, Nov 14, 2008 at 3:13 PM, ant elder <[EMAIL PROTECTED]> wrote:
> > > On Fri, Nov 14, 2008 at 9:39 AM, Simon Laws <[EMAIL PROTECTED]>wrote: > >> >> >> On Fri, Nov 14, 2008 at 9:22 AM, ant elder <[EMAIL PROTECTED]> wrote: >> >>> >>> >>> On Fri, Nov 14, 2008 at 8:52 AM, Ramkumar R <[EMAIL PROTECTED]>wrote: >>> >>>> On Thu, Nov 13, 2008 at 12:40 PM, Luciano Resende <[EMAIL PROTECTED] >>>> > wrote: >>>> >>>>> Hey Dave >>>>> >>>>> With the results from [1], I guess we are ready to cut the 1.x >>>>> branch where any work necessary for a 1.4 release can be done. As for >>>>> the 1.4 release plans, we probably need to revise the plans and >>>>> schedule, but any help on getting the release out from others on the >>>>> community is certainly welcome. >>>>> >>>>> [1] http://markmail.org/message/na5r3ghoji6nqlzw >>>> >>>> >>>> Hi Luciano, >>>> >>>> I would be very much interested in getting involved with the release >>>> activities in getting the release done for 1.4. >>>> >>>> Please let me know, where to start and how to proceed further? Thanks. >>>> >>>> -- >>>> Thanks & Regards, >>>> Ramkumar Ramalingam >>>> >>> >>> Here's some things that need to happen: >>> >>> Firstly make the release branch from trunk/1.x >>> - create the 1.4 branch by doing an svn copy from 1.x to 1.4 >>> - rename the version in the trunk/1.x to be 1.5-SNAPSHOT >>> >>> Complete build of 1.4 including distribution >>> >>> Start reviewing and testing the 1.4 distribution >>> - legal: >>> --compare the jars in the lib folder to whats in the 1.3.2 release lib >>> folder and note differences >>> --compare the LICENSE and NOTICE with whats in 1.3.2 distribution and >>> note the differences >>> - try out all the samples, demos and tutorials checking they still work >>> as described in the READMEs raising JIRAs for any problems >>> >>> ...ant >>> >>> >> As we haven't done a release for a while out of 1.x (we've been doing 1.3 >> releases) can I suggest we do all the tidying work in 1.x before cutting the >> release branch. A matter of building the distro ourselves and making sure >> the samples run, fixing up the licenses etc. Should save a bit of time in >> terms of copying changes back and forth. >> >> Once we have the distro pretty tidy we can fall back into the process Ant >> describes for a final scrub and RC production. >> >> Simon >> > > Actually thats a good point, and as 1.x will be pretty stable as we're > focusing on 2.0 it should be fine doing the tidy up directly in the 1.x > branch for now. > > ...ant > Thanks Ant and Simon for the inputs, to start with I will do this as discussed.... Complete build of 1.x including distribution Start reviewing and testing the 1.x distribution - try out all the samples, demos and tutorials checking they still work as described in the READMEs raising JIRAs for any problems -- Thanks & Regards, Ramkumar Ramalingam
