Inline
On Feb 23, 2009, at 1:51, Isabel Drost <[email protected]> wrote:
On Sunday 22 February 2009, Grant Ingersoll wrote:
Maven does the tag automatically. I figured the branch was only
necessary once the process was figured out. Feel free to delete the
tag, too.
Ah. Now I understand. So the intented process for us is: Freeze
trunk, do the
release, create the tag, release trunk for new contributions. Right?
Yes
Some additional information for releasing:
1) Generate a PGP key for signing releases, if you do not have one
already.
2) Profile to use for releasing: mahout_release
3) Maven settings.xml I used (all lines starting with $ replaced
with my
personal settings):
<settings>
<profiles>
<profile>
<id>mahout_release</id>
<properties>
<deploy.url>scpexe://people.apache.org:~/public_html/$repo/</
deploy.url>
<username>$username</username>
</properties>
<repositories>
<repository>
<id>Staging</id>
<url>http://people.apache.org/~$username/$repo</url>
<snapshots><enabled>true</enabled></snapshots>
<releases><enabled>true</enabled></releases>
</repository>
</repositories>
</profile>
</profiles>
</settings>
I think I had a few other options, but I'm not at my computer. I'll be
back on Thursday and can upload. I think I pot stuff up on the How to
Release section of the wiki.
4) You want to use ssh_agent for uploading to apache servers. But
then again,
you probably have set this up already.
Other than that everything is basically maven standard release
procedure.
----
Up to now I have only issued mvn deploy - the results can be found in:
http://people.apache.org/~isabel/staging-repo/
Will try release:* later this week. Grant, if you happen to have
time earlier,
feel free to take over.
Yep will do on Thurs.
One question: The unit tests are currently configured such that they
cannot be
disabled with -Dmaven.test.skip. For testing my environment and
various
settings (for the assembly plugin, for the deployment and the like)
I would
very much like to have the option of switching the tests off. Any
objections
to removing the sure-fire option that prevents that? If I have
missed some
way to do this already: what did I miss?
Try skipTests instead. Maven seems to not care about back compat
Another thought about the tests: I think it would make sense to
split the
tests into unit tests (running quickly, executed at every built) and
integration tests (taking more time, executed at every release). I
don't
think that is necessary for 0.1 - but it would be nice to do this
before the
next release. Any suggestions?
I have updated the KEYS file to contain the public part of the key I
used for
signing the artifacts, will commit this information this evening
(Upload of
the last artifact is still running - slow DSL uplink sucks). I have
NOT used
the key I usually sign my mails with. Question: Is there a general
way to
tell maven which key to use for signing artifacts?
Have a look at the Gpg plugin. I imagine there is.
So far I have not recreated the tag with maven. I have checked in
the changed
KEYS file into trunk.
Isabel
--
The hatred of relatives is the most violent. -- Tacitus (c.55
- c.117)
|\ _,,,---,,_ Web: <http://www.isabel-drost.de>
/,`.-'`' -. ;-;;,_
|,4- ) )-,_..;\ ( `'-'
'---''(_/--' `-'\_) (fL) IM: <xmpp://[email protected]>
