I believe that the main reason for this mess is our poor release frequency. If we can do a release at least once every 3-4 months, trunk and everything else will stabilize gradually. Part of my recent efforts with the new documentation, integration tests and dependency cleanup was intended to lay a foundation on which we can do quick and frequent releases with small incremental improvements. This release has been a great learning experience so far. We are learning where things have gone wrong and are actively taking action to fix them.
Thanks, Hiranya On Tue, Dec 27, 2011 at 7:41 PM, Andreas Veithen <andreas.veit...@gmail.com>wrote: > On Tue, Dec 27, 2011 at 06:02, Hiranya Jayathilaka <hiranya...@gmail.com> > wrote: > > > > > > On Tue, Dec 27, 2011 at 4:58 AM, Andreas Veithen < > andreas.veit...@gmail.com> > > wrote: > >> > >> -1 > >> > >> The Maven artifacts don't meet the requirements for publication to > >> Maven Central (see [1] and in particular the link to [2]). In > >> particular each artifact must be signed. Each artifact must also have > >> an MD5 checksum (that is not explicitly mentioned in [2] because the > >> maven-deploy-plugin normally takes care of this). > >> > >> I'm not even sure if releasing artifacts using the old > >> m2-ibiblio-rsync-repository thing is still supported. What is sure is > >> that the only documented way is via Nexus. > > > > > > Can you please explain how that's done? Should we follow the instructions > > on http://www.apache.org/dev/publishing-maven-artifacts.html? > > > >> > >> > >> There is also a regression with respect to the project branding > >> requirements. Apparently the change in r1051752 was never applied to > >> the trunk and is missing in 2.1.0. > > > > > > No it is available in 2.1. Take a look at the links available on the Main > > Menu of the site. It's not yet committed to the trunk. But we still > haven't > > merged the new documentation into the trunk. That will be done pretty > soon. > > The change not only modifies the links, but also adds a disclaimer > related to trademarks. It's not included in 2.1 and if you now replace > the documentation on the trunk with the one from the 2.1 branch, it > will be definitely lost. Obviously it is easy to add that again, but > I'm pretty sure that this will not be the only change that is lost in > the process. > > I would strongly recommend that before continuing with the effort to > release 2.1 the project sorts this out and establishes a clear > branching strategy to stop that mess. Otherwise the 2.2/3.0 release > will be even worse. > > > Thanks, > > Hiranya > > > >> > >> That seems to be a general problem > >> in the Synapse project, namely that there is no effective strategy to > >> manage the release branch and to ensure that all relevant changes are > >> in the trunk. In Axis2/Rampart/Sandesha2 we have eradicated that > >> problem by using a consistent (yet simple) strategy to manage the > >> release/maintenance branches. > >> > >> Andreas > >> > >> [1] http://www.apache.org/dev/publishing-maven-artifacts.html > >> [2] > https://docs.sonatype.org/display/Repository/Central+Sync+Requirements > >> > >> On Mon, Dec 26, 2011 at 16:30, Kasun Indrasiri <kasun...@gmail.com> > wrote: > >> > Hi Devs, > >> > > >> > This is the call for votes to release Apache Synapse-2.1.0. > >> > > >> > Please review the signed artifacts: > >> > http://people.apache.org/~kasun/synapse/2.1-RC1/artifacts/ > >> > > >> > The m2 repository is available at: > >> > http://people.apache.org/~kasun/synapse/2.1-RC1/m2_repo/ > >> > > >> > Revamped site for this release is available at: > >> > http://people.apache.org/~kasun/synapse/2.1-RC1/site/ > >> > > >> > SVN Info: > >> > revision is 1222784 on > >> > https://svn.apache.org/repos/asf/synapse/branches/2.1 > >> > > >> > Here is my +1 to declaring the above dist as Synapse-2.1.0. > >> > > >> > Thanks, > >> > -- > >> > Kasun Indrasiri > >> > Associate Technical Lead, > >> > WSO2 Inc. - "Lean . Enterprise . Middleware" - http://www.wso2.com/ > >> > Blog : http://kasunpanorama.blogspot.com/ > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org > >> For additional commands, e-mail: dev-h...@synapse.apache.org > >> > > > > > > > > -- > > Hiranya Jayathilaka > > Associate Technical Lead; > > WSO2 Inc.; http://wso2.org > > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 > > Blog: http://techfeast-hiranya.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org > For additional commands, e-mail: dev-h...@synapse.apache.org > > -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
