You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by Mohammad Nour El-Din <no...@gmail.com> on 2011/05/17 20:03:45 UTC
[URGENT] - Attention: Undergoing release process
Hi all...
Please *stop* doing any commits on the *trunk* till further notice,
Dan is working on creating 0.1.2-incubating release artifacts.
--
Thanks
- Mohammad Nour
Author of (WebSphere Application Server Community Edition 2.0 User Guide)
http://www.redbooks.ibm.com/abstracts/sg247585.html
- LinkedIn: http://www.linkedin.com/in/mnour
- Blog: http://tadabborat.blogspot.com
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
"Writing clean code is what you must do in order to call yourself a
professional. There is no reasonable excuse for doing anything less
than your best."
- Clean Code: A Handbook of Agile Software Craftsmanship
"Stay hungry, stay foolish."
- Steve Jobs
Re: [URGENT] - Attention: Undergoing release process
Posted by Dan Haywood <dk...@gmail.com>.
Hi Mark,
You are right that -P apache-release does a lot of the work, but that's
not the full story. I was at the Apache retreat in Ireland this last
weekend getting as much info as I can on how to do a release. In
addition to using -P apache-release, I also learnt about:
* the RAT tool doesn't seem to work correctly (the excludes property to
exclude generated files doesn't seem to work)
* to use maven-remote-resources-bundle-plugin (and its associated
src/main/appended-resources/supplemental-datamodels.xml) for grafting in
missing license info for 3rd party dependencies
* include apache-incubator-disclaimer-resources in the above bundle to
ensuring that the DISCLAIMER appears in every META-INF/MANIFEST.MF
* the need to include additional advertising clauses of 3rd party
dependencies in the NOTICES file if required (eg for Apache 1.0 /1.1
dependencies)
* I think this will might require a customization of the default
apache-jar-resource-bundle in order to allow the content of NOTICES to
be fine-tuned
* what is actually voted on (ie the source-release.zip)
* resolving a multitude of release:prepare issues
* where to put the scm/url entry (just in the parent root)
* that it fails with a NullPointerException if using cygwin on
Windows (solution: use CMD.EXE or UN*X)
* the "European problem", which causes release:prepare to fail when
tagging
* suggestion to use RCn for tagging prior to actual release
* suggestion to rehearse by using a branch
* remember to edit scm entries in release parent
* to use subkeys with an expiry date for signing rather than signing
* how to push out a release after a vote by copying to "dist"
* load key up to id.apache.org so that it can be signed (we had a
signing party, so should be ok to sign with my key now)
I've also put a picture onto our wiki [1] along with which explains the
process as I see it. I need to write up my notes, which I intend to do
this week.
If you have any corrections or clarifications, then let me know.
Also, one thing I'm still not completely sure about: how does one
specify that a subkey should be used for signing rather than my parent
key? Again, if you know, then let me know!
Cheers
Dan
[1] https://cwiki.apache.org/confluence/display/ISIS/ReleaseProcess
On 18/05/2011 12:12, Mark Struberg wrote:
> hi, if we have the latest apache-parent then you dont need anything for getting a source package. Just use -Papache-release ...
>
> Donald Woods wrote a very goot summary about it:
>
> http://incubator.apache.org/bval/cwiki/release-process.html
>
> That might help. We are basically also using the same process for releasing OpenWebBeans, MyFaces and OpenJPA.
>
> LieGrue,
> strub
>
> --- On Wed, 5/18/11, Dan Haywood<dk...@gmail.com> wrote:
>
Re: [URGENT] - Attention: Undergoing release process
Posted by Mark Struberg <st...@yahoo.de>.
hi, if we have the latest apache-parent then you dont need anything for getting a source package. Just use -Papache-release ...
Donald Woods wrote a very goot summary about it:
http://incubator.apache.org/bval/cwiki/release-process.html
That might help. We are basically also using the same process for releasing OpenWebBeans, MyFaces and OpenJPA.
LieGrue,
strub
--- On Wed, 5/18/11, Dan Haywood <dk...@gmail.com> wrote:
> From: Dan Haywood <dk...@gmail.com>
> Subject: Re: [URGENT] - Attention: Undergoing release process
> To: isis-dev@incubator.apache.org
> Date: Wednesday, May 18, 2011, 7:34 AM
> Hi Nour/all,
>
> I'm gonna be cutting an RC1 release this Sunday, so please
> make sure you have all commits in by end of play
> Saturday. (I'm just doing a little tidy up myself... I
> want to remove the 'release' module in order that we can
> release everything as a single voteable source.zip, rather
> than as several).
>
> Cheers
> Dan
>
>
> On 17/05/2011 19:03, Mohammad Nour El-Din wrote:
> > Hi all...
> >
> > Please *stop* doing any
> commits on the *trunk* till further notice,
> > Dan is working on creating 0.1.2-incubating release
> artifacts.
> >
>
Re: [URGENT] - Attention: Undergoing release process
Posted by Dan Haywood <dk...@gmail.com>.
Hi Nour/all,
I'm gonna be cutting an RC1 release this Sunday, so please make sure you
have all commits in by end of play Saturday. (I'm just doing a little
tidy up myself... I want to remove the 'release' module in order that we
can release everything as a single voteable source.zip, rather than as
several).
Cheers
Dan
On 17/05/2011 19:03, Mohammad Nour El-Din wrote:
> Hi all...
>
> Please *stop* doing any commits on the *trunk* till further notice,
> Dan is working on creating 0.1.2-incubating release artifacts.
>