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 > >
