Can we somehow find out whether it's just PMC members who are allowed to stage
releases at nexus?
Uli
On 18.12.2009 11:12 schrieb Andreas Andreou:
hmm - and something related... I'm not sure how important it is, but
according to
http://maven.apache.org/developers/release/pmc-gpg-keys.html
keys should also be found at http://pgp.mit.edu/
Also, the url of that contains PMC which got me thinking and I'm not
sure if i've read it somewhere, but i have the feeling only PMC can
stage releases at nexus - i gotta run for a few hours, so, can't quite
check it out right now :(
On Fri, Dec 18, 2009 at 12:07, Andreas Andreou<[email protected]> wrote:
ok, based on Ulrich feedback and ... parts of myself, i've moved the
Binary / Source Distributions step back before the voting step, fixed
1-2 links that
were not showing and and updated
http://people.apache.org/~andyhot/tapestry-site/dev/checklist-new.html
So, I'd also like to try it on 5.0 myself, are you ok in doing 5.1 ?
I'm thinking for later tonight or (at worst) at some time on Saturday...
Is there something wrong if we do both at basically the same time?
On Fri, Dec 18, 2009 at 09:26, Igor Drobiazko<[email protected]> wrote:
No more comments. I suppose we can go ahead with the releases. I would like
to try the new release process this weekend.
On Mon, Dec 14, 2009 at 9:10 AM, Andreas Andreou<[email protected]> wrote:
Hi,
i've documented the new release process at :
http://people.apache.org/~andyhot/tapestry-site/dev/checklist-new.html<http://people.apache.org/%7Eandyhot/tapestry-site/dev/checklist-new.html>
For comparison, the previous process is at :
http://people.apache.org/~andyhot/tapestry-site/dev/checklist.html<http://people.apache.org/%7Eandyhot/tapestry-site/dev/checklist.html>
The process can be summarized as:
1) mvn release:prepare
2) mvn release:perform
3) Login to Nexus, 'close' automatically created staging repository
and note its url.
4) Send vote email ... 3 days pass
5) Login to Nexus and promote the release
6) Generate and upload Binary / Source Distributions (currently needs ant)
7) Once files reach all mirrors, update the Downloads Page
Steps 1-5 are really straightforward/automated (meaning that no manual
copying of
files is needed).
The artifacts of step 6 could perhaps also be generated by maven (and thus
be staged as well) but i'm not sure if we can spend time on this right now.
Because of that (and that's the only difference to the previous workflow),
i've moved the Binary / Source Distributions step at the very end,
i.e. after the
vote has passed. Is that a deal-breaker? The alternative would be to move
that
step just before step 4.
So, please take a look and comment if something needs more explanation
or changes.
--
Andreas Andreou - [email protected] - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Best regards,
Igor Drobiazko
http://tapestry5.de/blog
--
Andreas Andreou - [email protected] - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
