Hi Alex, thanks for the information... I'm going to use branch for my custom developments, as it's not possible to test the changes in the unstable trunk.. I'll get them ported whenever the merging is done..
thanks, Thilina On 11/3/07, Alex Boisvert <[EMAIL PROTECTED]> wrote: > Hi Thilina, > > We are doing development on both 1.1 branch and the trunk. The main > guideline is that all bug fixes and enhancements made to the 1.1 branch are > also ported to the trunk in a timely manner (where applicable). We want to > avoid a big-bang porting effort when we decide to close the 1.1 branch. > > The trunk is a refactored codebase intended to better support different > messaging styles (blocking, async, reliable, transacted). It is usable but > no yet as stable as 1.1. We welcome development, testing and feedback on > the -trunk. > > I would say use 1.1 if you need the feature integrated in a stable build in > the short-term (1-2 months) and it can be easily ported to the trunk (e.g. > the feature doesn't involve messaging styles). Otherwise I would use the > trunk right away. > > alex > > > On 11/2/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > > > > Hi Devs, > > I'm thinking of doing some custom changes over ODE, of which some > > might eventually be submitted as patches.. These changes will mostly > > focused on the web services layer.. > > > > On which branch I should do my changes?? ..I prefer to do my > > developments on 1.1 branch, as it is the stable branch.. But if > > everybody started developing on the 1.1 branch in addition to trunk, > > then I foresee a merging nightmare in this project.. > > > > Is there a planned date for merging the 1.1 branch with the trunk?.. > > IMHO having a unstable trunk is not that appealing for the new users > > and for the prospective developers. > > > > thanks, > > Thilina > > > > -- > > Thilina Gunarathne - http://thilinag.blogspot.com > > > -- Thilina Gunarathne - http://thilinag.blogspot.com
