On 14/10/11 18:07, Paolo Castagna wrote:
Short summary:
- trunk is always in development mode and dependencies on our modules are all
-SNAPSHOT dependencies
- committers can run mvn deploy whenever they need, no problem
- we should have candidate releases in our staging repository, the release
manager can put stuff there via mvn release:prepare, etc.
There's a profile to use:
mvn clean deploy -Papache-release
[[
Create a source-release artifact that contains the fully buildable
project directory source structure. This is the artifact which is
the official subject of any release vote.
]]
- people have three choices (level of risk/bleeding edge): snapshots (high
risk), candidate releases (medium risk), official Apache releases (low risk)
Andy
