...
1 | Update the POMs to remove "-SNAPSHOT" from the version | ||
---|---|---|---|
2 | Commit the POM changes | ||
3 | Tag the release by making a SVN copy of the head or designated revision | ||
|
| ||
4 | Assemble the release (see notes) | ||
|
| ||
5 | Sign the release artifacts (in | ||
|
| ||
6 | | ||
7 | Deploy the artifacts to our Maven repository | ||
|
| ||
| Prune any obsolete snapshots from | ||
8 | Update the POMs to next version number and add the "-SNAPSHOT" suffix | ||
9 | Commit the POM changes | ||
10 | Deploy the new snapshot | ||
|
| ||
11 | Add the next version to our issue tracker for scheduling new features and fixes | ||
12 | If the distribution is being mirrored, copy the ZIPs to {/www/www.apache.org/dist/struts}}, wait 24 hours, and then update the |
One time
Create and install a SSH key
...
Interim Notes on Cobbling a Distribution
...
Assembling a Struts 2 distribution is not fully automatic. For the time being, there are a few extra steps.
- Extract assembly to a root drive (\struts-2.0.
...
- x)
- Download the WW documentation archive from http://struts.apache.org/WW
...
- .zip
- Extract archive under the
docs
folder
Create updated archives for
- struts-2.0.x-docs.zip
- struts-2.0.x-all.zip
To update the Java 4 distribution, we need to
- Copy the "backport" folder that is under SVN.
- If needed, update the translator JARs and translate batch file
- If needed, update the translate batch file as to the Struts version
- run the translate batch file
- update struts-2.0.x-j4.zip archive
Obviously, we'd prefer that the entire build process was automatic, as it has been before. But this is how things stand right now.