yes if every new major feature did this it would be great. +1 ========================= BJ Freeman http://bjfreeman.elance.com Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93> Specialtymarket.com <http://www.specialtymarket.com/>
Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Linkedin <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro> Jacopo Cappellato sent the following on 4/6/2010 11:07 PM: > I would suggest to: > 1) release 10.04 before the merge is done > 2) merge the code to the trunk, switch to it, fix any possible issue > 3) do another release (10.06?) > > I know this is not inline with what we currently think a release should be, > but this is very inline with what the ASF practices and so I will continue to > insist with the release-often practice. :-) > > Jacopo > > On Apr 4, 2010, at 8:21 PM, Adrian Crum wrote: > >> I would like to start bringing parts of the executioncontext20091231 branch >> into the trunk before we create the next release branch. The implementation >> of the new security design is not finished, but it will be disabled - so >> everything will still work the same. >> >> My goal is to allow users of the 10.x release to plan for the forthcoming >> changes, and maybe have the conversion to the new design completed by the >> release that follows 10.x. >> >> I will wait a few days, and if there are no objections I will begin merging >> the design into the trunk. >> >> -Adrian >> >> >> >> > >
