hi, I think GUI issues are not highly critical issues since those features anyway can be done by using configuration files. But if we have CLOSE_WAIT issue it is a good enough reason to go for a new release. Actually I sent a mail regarding this before the release and there was no any response.
What about doing a 1.6 release after 2-3 months time. As I remember we cut the 1.5 branch last year. And there may be more this kind of issues being reported by that time. thanks, Amila. On Thu, Jun 11, 2009 at 3:25 AM, Andreas Veithen <andreas.veit...@gmail.com>wrote: > [Switching to dev list; first part of the discussion is in AXIS2-4371] > > +1, Andreas. Can you merge your fixes over to the branch and I'll update > the version number over there? > > Does it mean that we continue to use the existing 1.5 branch? Do we > have a tool (Maven release plugin?) to change the version numbers or > can this only be done manually? > > There is also another decision to take: if we start to work on 1.5.1, > we will run again into the module version mess: we will have to use > 1.51 instead of 1.5.1 for the version number of all modules. I fixed > this issue on the trunk (see AXIS2-4034), so we need to decide if we > merge these changes to the 1.5 branch. Note that the price to pay is a > minor API change in the AxisModule class (the version attribute is no > longer a String, but a Version object). > > Andreas > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
