Unfortunately the last RC will be the release ... that's why I would publish a release of each RC to the Staging repo. If the release passes, the release goes out the door ... if not the staging repo is dropped and nothing goes out the door.
I didn't quite get that Alex didn't stage an official RC .. so I'll probably just publish an up to date SNAPSHOT the same way I did the last few weeks. As soon as the RC is prepared by Alex, I'll stage the RCs in the repo and drop/release the repo in sync with Alex ... would that be ok? But now I have to catch my flight ... CU Chris -----Ursprüngliche Nachricht----- Von: omup...@gmail.com [mailto:omup...@gmail.com] Im Auftrag von OmPrakash Muppirala Gesendet: Freitag, 25. September 2015 09:28 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: [DISCUSS] Release Apache Flex FalconJX 0.5.0 I think this is how it should map: Release Candidate artifacts == SNAPSHOT Released artifacts == RELEASE On Fri, Sep 25, 2015 at 12:21 AM, Alex Harui <aha...@adobe.com> wrote: > > > On 9/25/15, 12:16 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: > > >Well I deffinitely won't have time to do the entire release process. > >You allready staged a "normal" release, all I would do would be to > >download that ... change the "SNAPSHOT" in the maven.xml to "RELEASE" > >and execute "ant -f maven.xml deploy" ... that should be all. I could > >do that from the hotel this eavening or some time during the day tomorrow. > > I think I’m confused. The links I posted are for artifacts to be > considered for release. It isn’t even an official release candidate, > or been voted on, so I’d consider it a snapshot. But I hope you’ll be > able to do what you described before ApacheCon is over if not sooner. > > Thanks for helping out, > -Alex > >
