On Sat, Jun 4, 2011 at 22:51, Mark Thomas <[email protected]> wrote: > On 04/06/2011 21:45, Andreas Veithen wrote: >> On Sat, Jun 4, 2011 at 22:07, Mark Thomas <[email protected]> wrote: >>> On 04/06/2011 21:02, Andreas Veithen wrote: >>>> Axis2/C has not yet done any release since the migration to the Axis >>>> TLP. 1.5.0 and 1.6.0 are the last two major releases. That should be >>>> OK with respect to the archiving policy. >>> >>> It would if there was some indication that 1.5.x was still being >>> developed but since only 1.6.0 is listed on the Axis C download page, >>> 1.5.0 looks like an old release that needs to be removed. If 1.5.x was >>> still under active development in parallel with 1.6.x I'd expect to see >>> it listed on the download pages. >> >> It is listed: >> >> http://axis.apache.org/axis2/c/core/download.cgi >> >> Probably you are confusing Axis2/C with Axis/C++. > > Nope, I was just looking here: > http://axis.apache.org/axis2/c/core/ > > I still see no good reason for anything other than 1.6.0 to be on the > mirrors. There is no evidence of parallel development of branches here, > just serial releases.
I can only give authoritative answers to questions about the Java projects in Axis. I honestly don't know if there is any chance that there will be an Axis2/C 1.5.1 release or if any of the other C projects is still based on 1.5.0 and has not yet upgraded to 1.6.0. I did the requested cleanup for Axis and the WS subprojects I'm actively involved in back in March. To me, having a 1.5.0 release and a 1.6.0 release seemed to be compatible with the scheme outlined in your mail from March 13: a) latest release of the current branch b) latest stable release of the current branch c) latest stable release of previous branches If you need evidence of parallel development for each and every project that has more than a single release in the dist area, then this goes beyond what you requested initially. In the case of Axis2/C, I would first have to find somebody who can answer that question and who takes the necessary actions if 1.5.0 should be archived. I think it's important to reduce the amount of releases in the dist areas, but is it reasonable to push it to that level for each border case? I just happen to be the poor guy who today did the work that my fellow WS devs failed to do over the last couple of months, and now I'm dragged into a discussion about whether Axis2/C 1.6.0 is a release from a different branch or a serial release. I think we both have more important items on our todo lists than doing that kind of investigation, don't we? > Mark > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
