Hi Andy, sorry, I misunderstood what you meant. I will start a new thread with the pointers to the correct locations.
Greetings, Sebastian 2013/3/19 Sebastian Schaffert <[email protected]> > > Am 19.03.2013 20:18 schrieb "Andy Seaborne" <[email protected]>: > > > > > On 19/03/13 17:53, Sebastian Schaffert wrote: > >> > >> Hi Andy, > >> > >> actually the vote mail is already generated automatically from a > template > >> by the Maven Release Build (stole it from Jackrabbit). But I cannot > figure > >> out automatically the name of the staging repository. I will put on the > >> checklist to update the repository URL when writing the vote mail. > > > > > > Looking at [1], I see: > > > > 1/ The release candidate is a zip of the tagged svn. > > 2/ There is a URL to the maven staging area. > > > > Not sure that the release plugin has all the features needed and may be > missing support for the detail of marmotta's setup. > > > > The release is actually performed using exactly the same build I used over > the weekend, the release plugin only does the following: > - update the version number in all pom files to release > - create a tag in the GIT repository > - checkout the tag into a second repository to do a clean build > - run a clean distribution build creating all Maven artifacts and > distribution archives *in the clean checkout* > > The results of this clean build are the ones I uploaded. > > > > >> Sorry, forgot to push (we disabled automatic push by Maven because it > was > >> creating a bit of a mess when preparing the release). Just pushed now, > >> there is a tag "3.0.0-incubating". > > > > > > Wow - I see 83 files changed as part of that commit. > > > > Personally I'd restart the VOTE with the right information in the call. > The files (which I haven't had a chance to look at yet!) can be the same. > > > > No worries, the uploaded distribution files are exactly from this build > with this tag. If you have a look, the only difference is the updated > version number in the POM file. > > Everything was committed just fine to my local repository before the > release build, I just didn't synchronise with the upstream repository (GIT > involves first a local commit and then a push to upstream in which nothing > is changed). > > Greetings, > > Sebastian > > > Andy > > > > [1] > http://mail-archives.apache.org/mod_mbox/jackrabbit-dev/201302.mbox/%3CCAOFYJNZpUnHnKtDZp-zrjCgcey8kugTrJNE9J3Qwq5bTZTRBkg%40mail.gmail.com%3E > > > > > > > >> > >> Greetings, > >> > >> Sebastian > >> > >> > >> 2013/3/19 Andy Seaborne <[email protected]> > >> > >>> On 19/03/13 16:54, Sebastian Schaffert wrote: > >>> > >>> A staged Maven repository is available for review at: > >>>> > >>>> > >>>> https://repository.apache.org/ > >>>> > >>> > >>> Presumably you mean: > >>> > >>> https://repository.apache.org/**content/repositories/** > >>> orgapachemarmotta-006/< > https://repository.apache.org/content/repositories/orgapachemarmotta-006/> > >>> > >>> > >>> Please link to a specific one: the vote thread is a long-term record > and > >>> this is going to go away and maybe be replaced in another release > cycle. > >>> If you end up with multiple, close together staging repos, it can > become > >>> unclear as to which is which. > >>> > >>> Andy > >>> > >>> PS Don't worry - once you have a template VOTE message, the next > release > >>> is a matter of remembering to update the details. > >>> > >> > > >
