Le 7/17/13 1:19 AM, sebb a écrit : > On 16 July 2013 23:18, Julien Vermillard <[email protected]> wrote: >> On Tue, Jul 16, 2013 at 11:18 PM, sebb <[email protected]> wrote: >>> On 16 July 2013 19:59, Julien Vermillard <[email protected]> wrote: >>>> Hi ! >>>> After some NOTICE and LICENSE file fixes (thanks Emmanuel!) >>>> Here the first milestone release for MINA 3. >>>> >>>> A temporary tag has been created (it can be removed if the vote is not >>>> approved): >>>> GIT tag : "3.0.0-M1" SHA-1 : "ae50b809006efcd99fd68a9ba2be713c7d917756" >>> Where is the Git repo to which that tag applies? >> The MINA git repo. git clone it and checkout the tag, if you have >> troubles we can provide you some support. >> Here the pointers : http://mina.apache.org/mina-project/sources.html >> >>> It needs to be listed in the vote e-mail please. >>> >>>> Please take a look at the artifact here : >>>> http://people.apache.org/~jvermillard/mina-3.0.0-M1-vote/ >>>> >>>> KEY file : http://apache.org/dist/mina/KEYS >>>> and vote : >>>> >>>> [ ] +1 release Apache MINA 3.0.0-M1 >>>> [ ] +0 I don't care >>>> [ ] -1 don't release ! >>>> >>>> PS : sorry no maven staging due to some nexus fuckup (it's listed in >>>> nexus but the URL give a 404) >>> Did you close the staging repo? >>> There's an open one in your name. >>> They are not visible as URLs until they are closed. >> I had some mysterious "host not found" error while maven-release was >> creating it.. so I gave up > It won't be possible to release to Maven without a valid Nexus staging > directory so that must not be ignored. > Given that the Maven jars include source, it's not a valid VOTE if > some of the source is not available to vote on. > > Please login to Nexus and check whether all the expected files are > present, and then close the staging directory. > It will then be available for the vote. > > Without that, I am voting -1 as the data for the vote is not complete. I have to -1 too this release, as the binary package contains sources. I just fixed the cause (bin.xml was incorrect).
I will try to cut a new release today. Note that there is nothing wrong with cancelling releases : we are testing the first release for 3.0-M1, with git, and it's not easy to tune the various knobs that make it a valid release ! -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
