On Tue, Dec 27, 2011 at 7:00 PM, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Tue, 2011-12-27 at 12:53 +0530, Ruwan Linton wrote: > > Kasun, also make sure to run the generated site through a link checker > > too. > > > > Assuming there will eventually be another RC, could you also please > consider upgrading HttpCore dependency to the latest GA release (4.1.4)? > Yup. Will do. Thanks Oleg. -Hiranya > > Cheers > > Oleg > > > Thanks, > > Ruwan > > > > On Tue, Dec 27, 2011 at 12:49 PM, Ruwan Linton > > <ruwan.lin...@gmail.com> wrote: > > > > > > On Tue, Dec 27, 2011 at 12:09 PM, Hiranya Jayathilaka > > <hiranya...@gmail.com> wrote: > > > > > > On Tue, Dec 27, 2011 at 10:32 AM, 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? > > > > > > I believe this is the right set of instructions. > > > > Yes, these are the instructions from Apache, and you will > > probably have to meddle a bit with the Nexus documentation on > > release staging [1] too. > > > > Thanks, > > Ruwan > > > > [1] - > > http://www.sonatype.com/books/nexus-book/reference/staging.html > > > > Kasun, shall we look into staging this release on > > Nexus? Out POMs already inherit from the root Apache > > POM (may be except for the xar plugin which we can > > fix). It also looks like Synapse project is already > > setup on Nexus. Like Ruwan said it seems the ground > > work is already done. > > > > > > Thanks, > > Hiranya > > > > > > > > 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. > > > > > > 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 > > > > > > > > > > -- > > 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 > > > > > > > > > > -- > > Ruwan Linton > > Member, Apache Software Foundation; http://www.apache.org > > Director of Engineering; http://adroitlogic.org > > > > phone: +94 11 282 7532 > > email: ru...@adroitlogic.com; cell: +94 77 341 3097 > > blog: http://blog.ruwan.org > > linkedin: http://www.linkedin.com/in/ruwanlinton > > google: http://www.google.com/profiles/ruwan.linton > > tweet: http://twitter.com/ruwanlinton > > > > > > > > > > > > -- > > Ruwan Linton > > Member, Apache Software Foundation; http://www.apache.org > > Director of Engineering; http://adroitlogic.org > > > > phone: +94 11 282 7532 > > email: ru...@adroitlogic.com; cell: +94 77 341 3097 > > blog: http://blog.ruwan.org > > linkedin: http://www.linkedin.com/in/ruwanlinton > > google: http://www.google.com/profiles/ruwan.linton > > tweet: http://twitter.com/ruwanlinton > > > > > > --------------------------------------------------------------------- > 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
