BTW, I guess code freezse for alpha means tagging the CVS for the release. Would it be OK if I commit to CVS head after the CVS is tagged, given that the tag is for alpha? Or do I have to wait till 28th when the alpha is released?
Thanks, Samisa... On Tue, 25 Jan 2005 15:23:04 +0600, sanjaya singharage <[EMAIL PROTECTED]> wrote: > Hi all, > > any feedback on this yet? > > Also are we going to include axis3transport for 1.5? I missed discussions on > this because I was on leave at that time. Just had a look at that thread. > > sanjaya. > ----- Original Message ----- > From: sanjaya singharage > To: [email protected] > Sent: Monday, January 24, 2005 2:10 PM > Subject: Axis c++ 1.5 release plan (draft 3) > > Hi Mark, John and all, > > From the C support point of view I think it is not prudent to go for 1.5 > code freeze without atleast client side support with stub generation. I hope > it is a date close to 25 th with that in place so that we can go for the > code freeze. > > Mark, John could we have a date as to when we could have that and go for > code freeze? > > ALSO COULD I HAVE WHO IS DOING WHAT AND THE STATUS OF ITEMS 4 AND 5 IN THE > FEATURE/IMPROVEMENT LIST BELOW? > (So that we know that the listed out items are all being done for 1.5) > > Following the discussion I have added these items > -Problem with complex types which contain complex types > http://issues.apache.org/jira/browse/AXISCPP-197 (in progress by carsten) > > Following the discussion I have removed the following items > > -Fault mapping (stub level) > -improvement of Web Site > a.Web-site should be made more or less like Axis-Java website for ease of > use > b.More user oriented and less developer oriented > > PLEASE SUGGEST A DATE FOR CODEFREEZE/RELEASE AND VOTE. > > sanjaya. > > ======================================================= > > (third draft of the release plan.) > > Hi all, > I would like to volunteer to be the release manager for the Axis C++ 1.5 > release. > > A draft Release Plan is presented below using the current items found in the > wiki at http://wiki.apache.org/ws/FrontPage/AxisC_2b_2b/ToDo1.5 . > Please update the wiki of any more items that are applicable to the 1.5 > release that developers are working on. > > Also we need to decide on dates for code freeze etc. and release dates at > the bottom. > Please comment. > > > > This is the release plan (draft) for Axis C++ version 1.5. Given below is a > snapshot > of all the changes for 1.5 since the 1.4 version. > > Changes from 1.4 to 1.5: > > Partial C support - http://issues.apache.org/jira/browse/AXISCPP-210 (in > progress by Mark) > -C clients with stub generation for simple types > -Porting of some C++ tests to C > Memory clean-up and fix - http://issues.apache.org/jira/browse/AXISCPP-149 > (in progress by Mark Whitlock as per JIRA) > Improve HTTP Support - http://issues.apache.org/jira/browse/AXISCPP-176 > (Done by Samisa as per JIRA) > Add support for xsd:any type (?) > Ability to add custom headers (?) > "100 Continue" support in axis2 transport > http://issues.apache.org/jira/browse/AXISCPP-311 (Done by Samisa) > Proxy support for axis2 transport > http://issues.apache.org/jira/browse/AXISCPP-325 (Done by Samisa) > Numerous memory leak fixes (Done by Samisa) > Problem with complex types which contain complex types > http://issues.apache.org/jira/browse/AXISCPP-197 (in progress by Carsten) > > Details on these features could be found on JIRA and the AxisCpp TODO wiki > page at http://wiki.apache.org/ws/FrontPage/AxisC_2b_2b/ToDo1.5 > > Release Criteria: > > - Functional tests pass > - Test on installation procedures > - Test on different versions of Apache web server(1.3.xx, 2.0.xx) > - Test samples on different platforms (Linux, Microsoft Windows) > - Fix blockers and most critical bugs that applies to 1.5 > > Dates: > > The following are the proposed dates for the release, opinions please: > Code freeze January 25, 2005 ?? > Release alpha version January 28, 2005 ?? > Release beta version ?? > Release 1.5 February 28, 2005 ?? > > > sanjaya. >
