530c640d4f
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@112724 13f79535-47bb-0310-9956-ffa450edef68
39 lines
1.3 KiB
XML
39 lines
1.3 KiB
XML
<?xml version="1.0"?>
|
|
|
|
<project
|
|
xmlns:j="jelly:core"
|
|
xmlns:maven="jelly:maven"
|
|
xmlns:define="jelly:define"
|
|
xmlns:deploy="deploy"
|
|
xmlns:util="jelly:util"
|
|
xmlns:log="jelly:log"
|
|
xmlns:m="maven">
|
|
|
|
<!-- ================================================================== -->
|
|
<!-- R E L E A S E T A G L I B R A R Y -->
|
|
<!-- ================================================================== -->
|
|
|
|
<!--
|
|
| Process for a release:
|
|
|
|
|
| o tagging cvs
|
|
| o building source distribution
|
|
| o building binary distribution
|
|
| o notifying lists - we need a mailtag that can deal with authorization.
|
|
| my smtp for example will not let me poke it without a password.
|
|
| o pushing out RSS feeds maybe to javablogs?
|
|
| o updating the <version/> element in the POM
|
|
| o updating changes document
|
|
| o updating the status page
|
|
| o flipping the site from HEAD to release and deploy the site
|
|
| o all SNAPSHOT references must be changed to timestamped versions
|
|
| o incrementing the version - what rules do we want to follow? they
|
|
| have to be documented so we need a document to adhere to.
|
|
|
|
|
| Q: so how do we find the latest timestamped version.
|
|
| A: when a snapshot is deployed we need a file with the real version
|
|
| of the latest snapshot.
|
|
-->
|
|
|
|
</project>
|