Hi Eric, First of all, if you see my second mail that I fired few minutes before... you will realize one of the ideas behind going for a 2.0. Since the XML Schema compliance will make some changes to the configuration language.
We can do a 1.3 from the branch, but we cannot just dump the release, we need to complete documentation, do testing and so forth, which will result in more work. Having the above said features on the trunk and the schema compliance sort of changes planned to go into the trunk. I don't like to waste time on those aspects on 1.3 branch. I am about to send a release plan, it will at least take another month for the 2.0 release, but will be much more effective the time than spending another 2 weeks and doing a 1.3 release, with lesser features than trunk. I agree the 1.3 release has been dragging which is main reason for this strategy, but I could guarantee that the same thing wont happen for the 2.0 :-) Being said all that, if the user community is really interested in the 1.3 we could of course go for it before 2.0. Thanks, Ruwan On Mon, Apr 26, 2010 at 10:45 AM, Hubert, Eric <eric.hub...@foxmobile.com>wrote: > Hi Ruwan, > > > > I have a set of new stuff in mind to be completed on the 2.0 release as > well. So if there is no objection I would like to bring in a release plan > to be executed with the set of features that we are going to do for the 2.0 > release of Synapse. > > WDYT? > > No objections – only thoughts… Why not just dropping the current 1.3-branch > and recreating from trunk to stabilize there? From a project perspective I > think it is important to release more frequently. I’m not quite sure whether > the new features really justify a major release. I would see this > differently, if we had done any incompatible changes or completely modified > the configuration language for example… Also if we now incorporate even more > features, the release, however we are going to call it, will take even > longer until it can get out. > > > > Regards, > > Eric > > > > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com
