Hi all; Well I also went through the JIRA list and found that there are a number of JIRAs that we have to fix before 1.0. So as you suggested lets go for RC2 on this Friday and keep that for about a week for review. Since we have considerable code changes it is better to do another RC before declaring 1.0.
So lets change the release plan as follows 20th April : code freeze for RC2 21st April : Axis2 1.0 RC2 26th April : Code freeze for 1.0 (we have to change the code only if we found bugs) 1st May : Axis2 1.0 thoughts ....... ? Ajith Ranabahu wrote: >Hi All, >It seems that a number of issues has been reported about the codegen >utility (probably caused by the major surgery we did for removing >WOM). So it seems to me that the code freeze tomorrow (19th Apr) is >not realistic. >Anyway it is better for us to do a RC2 release before 1.0 at this >state. So my suggesion is to do a RC2 by the end of this week (which >is a slightly more realistic timeline to fix all the issues). > >Thoughts ? > >-- >Ajith Ranabahu > > > > -- Thanks, Deepal ................................................................ ~Future is Open~
