Is the release over ?

I dont find it on maven central
Le 28 janv. 2014 01:46, "Charles Duffy" <char...@dyfis.net> a écrit :

> The keys are actually different -- the one used by the currently-posted
> .asc files is associated with Indeed, Inc. I'll be resigning the binaries
> after verifying that their Indeed signatures are intact (and moving them to
> dist.apache.org at that time).
>
> Expect a note in this thread when that happens.
>
>
> On Mon, Jan 27, 2014 at 6:42 PM, Nicolas Lalevée <
> nicolas.lale...@hibnet.org
> > wrote:
>
> >
> > Le 22 janv. 2014 à 00:52, Nicolas Lalevée <nicolas.lale...@hibnet.org> a
> > écrit :
> >
> > > I have found some issues. The source distribution seems to miss some
> > test files. I guess this has been the case for quite some time. And it is
> > "just" about the tests. And it is an RC. So OK for me. And I will fix
> that
> > soon in trunk.
> > >
> > > To avoid confusion and make things simpler, I suggest we modify the
> > release process to that everything goes through the svn of
> dist.apache.org,
> > and not use anymore people.apache.org. In the end, everything is
> > published there.
> > > And I'll modify in the doc of the release process the template of the
> > email of the vote to include a line that is referencing the svn tag. So
> > it's more difficult to miss it, and it is helpful to do review.
> > >
> > > I have tested the staging update site: works like a charm.
> > >
> > > So LGTM.
> > >
> > > I will cast my vote as soon as I can verify the signature of the
> > artifacts.
> >
> > You pushed some keys to the KEYS files, but it doesn't seems to be the
> > same as the one you used to sign the proposed artifacts.
> >
> > My gpg is asking for the key ID 93FB868A. Did I do something wrong or the
> > keys are actually different ?
> >
> > Nicolas
> >
> >
> > >
> > > Nicolas
> > >
> > > Le 21 janv. 2014 à 17:19, Charles Duffy <char...@dyfis.net> a écrit :
> > >
> > >> FYI --
> > >>
> > >> A tag at
> https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1now
> > >> exists. This differs from the branch head from which the binaries for
> > test
> > >> were built only inasmuch as its svn:externals specify a specific
> > revision
> > >> of the documentation build tools rather than leaving their revision
> > >> floating.
> > >>
> > >>
> > >> On Tue, Jan 21, 2014 at 6:54 AM, Charles Duffy <char...@dyfis.net>
> > wrote:
> > >>
> > >>> Howdy --
> > >>>
> > >>> I've attempted to follow the documentation at
> > >>> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
> > >>> http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html(as
> > >>> included-by-reference in the former) in preparing the above. That
> > said, it
> > >>> appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1
> > branch,
> > >>> from the present tip of which the binaries were built, but no
> > associated
> > >>> tag).
> > >>>
> > >>> I'll be sure to get KEYS up-to-date. Thank you for the pointers.
> > >>>
> > >>>
> > >>> On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig <bode...@apache.org
> > >wrote:
> > >>>
> > >>>> Hi Charles,
> > >>>>
> > >>>> we don't really release binaries, they are just a convenience.  All
> > that
> > >>>> matters as a release is the sources.
> > >>>>
> > >>>> I'm not sure there is anything documenting the release process for
> Ivy
> > >>>> but in general you create an svn tag and build source and binary
> > >>>> distributions from that.
> > >>>>
> > >>>> What you have built now is a binary for testing and you don't really
> > >>>> need to vote on that at all.  Just encourage people to try it out
> :-)
> > >>>>
> > >>>> If you want to perform some sort of test-release, have a look at
> > >>>> <http://svn.apache.org/repos/asf/ant/antlibs/ReleaseInstructions>
> and
> > >>>> similar instructions to get an idea of what is expected.
> > >>>>
> > >>>>> PS -- As this build was performed on hardware owned by Indeed,
> Inc.,
> > the
> > >>>>> binaries are signed with the du...@indeed.com GPG key. For any
> final
> > >>>>> release, I would be using hardware under personal control and a key
> > >>>>> associated with cdu...@apache.org.
> > >>>>
> > >>>> Please make sure whatever key you use is inside
> > >>>> https://dist.apache.org/repos/dist/release/ant/KEYS - if you need
> any
> > >>>> help committing it there, please yell.
> > >>>>
> > >>>> Cheers
> > >>>>
> > >>>>       Stefan
> > >>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> > >>>> For additional commands, e-mail: dev-h...@ant.apache.org
> > >>>>
> > >>>>
> > >>>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> > > For additional commands, e-mail: dev-h...@ant.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> > For additional commands, e-mail: dev-h...@ant.apache.org
> >
> >
>

Reply via email to