Yes, we realized we missed this step shortly after this email was sent. The
website is missing the step of uploading the key to pgpkeys.mit.edu, though,
which was leading to proxy errors. I will spend some time to clean up this
tutorial, perhaps adding some screenshots.
Kanak
> Date: Mon, 11 Nov 2013 19:09:50 -0800
> Subject: Re: Release from branch
> From: [email protected]
> To: [email protected]
> CC: [email protected]
>
> Did you follow the 5th step? You need to select the repository and close
> it. I see the status is still "open"
>
> go to https://repository.apache.org and close your staged repository. Note
> the repository url (format
> https://repository.apache.org/content/repositories/orgapachehelix-019/org/apache/helix/helix/0.6-incubating/)
>
>
>
>
>
> On Mon, Nov 11, 2013 at 6:28 PM, Kanak Biscuitwala <
> [email protected]> wrote:
>
> > Hi,
> >
> > It seems as if the instructions at
> > http://helix.incubator.apache.org/releasing.html are not fully correct. I
> > can run:
> >
> > mvn release:prepare release:perform -B
> >
> >
> > And it reports as successful and even creates the new git tag properly,
> > but I have no idea where the files actually went. The instructions
> > indicate that they would be at
> > https://repository.apache.org/content/repositories/orgapachehelix-019/...
> > but that and similar paths don't exist.
> >
> > From what I'm seeing, thing are getting uploaded to
> > https://repository.apache.org/service/local/staging/deploy/maven2/org/apach
> > e/helix/... and I'm not sure where they go after that. Thus, I am unable
> > to run the next step, which involves running release-script-svn.sh.
> >
> > Any idea what's going on?
> >
> > Thanks,
> > Kanak
> >
> > On 11/7/13 2:11 PM, "Olivier Lamy" <[email protected]> wrote:
> >
> > >mvn clean deploy (from the branch :-) )
> > >Or you mean a Jenkins in ASF instance?
> > >As long as version in poms are different (which is not the case
> > >currently) that's easy.
> > >Maybe just the master version to 0.7.0-incubating-SNAPSHOT.
> > >And I can add a job in ASF jenkins based on the branch helix-0.6.2-release
> > >Just let me know if that make sense.
> > >
> > >--
> > >Olivier
> > >
> > >On 8 November 2013 05:00, kishore g <[email protected]> wrote:
> > >> Thanks Olivier, is it possible to make a snaphot jar (generated from
> > >> branch) available on maven. Currently snapshot jars are available from
> > >> trunk, not sure how we can generate it from branch.
> > >>
> > >>
> > >> On Sun, Nov 3, 2013 at 8:25 PM, Olivier Lamy <[email protected]> wrote:
> > >>
> > >>> correct.
> > >>> BTW, I think it's a good workflow :-)
> > >>>
> > >>>
> > >>> On 1 November 2013 13:15, Vinayak Borkar <[email protected]> wrote:
> > >>> > AFAIK the Maven Release Plugin can be used to release from a git
> > >>>branch.
> > >>> > Just checkout the branch you want to release from and run mvn
> > >>> > release:prepare and mvn release:perform as usual.
> > >>> >
> > >>> > Vinayak
> > >>> >
> > >>> >
> > >>> >
> > >>> >
> > >>> > On 10/31/13 4:50 PM, Kanak Biscuitwala wrote:
> > >>> >>
> > >>> >> For a little more context, we're planning to initiate a release off
> > >>>a
> > >>> >> branch called helix-0.6.2-release which contains some cherry-picked
> > >>> fixes
> > >>> >> from master, as well as some fixes to maintain compatibility. Will
> > >>>the
> > >>> Maven
> > >>> >> release plugin support creating releases off branches that aren't
> > >>> master?
> > >>> >>
> > >>> >> Kanak
> > >>> >>
> > >>> >> ----------------------------------------
> > >>> >>>
> > >>> >>> Date: Thu, 31 Oct 2013 16:47:20 -0700
> > >>> >>> Subject: Release from branch
> > >>> >>> From: [email protected]
> > >>> >>> To: [email protected]
> > >>> >>> CC: [email protected]
> > >>> >>>
> > >>> >>> Hi, do we support release from a branch?
> > >>> >>>
> > >>> >>> Thanks,
> > >>> >>> Zhen
> > >>> >
> > >>> >
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> Olivier Lamy
> > >>> Ecetera: http://ecetera.com.au
> > >>> http://twitter.com/olamy | http://linkedin.com/in/olamy
> > >>>
> > >
> > >
> > >
> > >--
> > >Olivier Lamy
> > >Ecetera: http://ecetera.com.au
> > >http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
> >
