Fixed link and some general clean up.
Signed-off-by: WalkerWatch <ctwalker@gmail.com>
This commit is contained in:
WalkerWatch
parent
daa2a217e3
commit
c705c3fd98
|
|
@ -31,18 +31,15 @@ This release script is for jetty-9 (to release jetty-7 or jetty-8 see older docu
|
|||
These follow a strict format and will be used when prompted during step link:#prepare-release-step[listitem_title] below.
|
||||
+
|
||||
....
|
||||
|
||||
Release Version : 9.0.0.v20130322 (v[year][month][day])
|
||||
Next Development Version : 9.0.1-SNAPSHOT
|
||||
Tag Name : jetty-9.9.0.v20130322
|
||||
|
||||
|
||||
....
|
||||
|
||||
2. We use the 'release-9' branch to avoid problems with other developers actively working on the master branch.
|
||||
+
|
||||
[source, screen, subs="{sub-order}"]
|
||||
....
|
||||
|
||||
// Get all of the remotes
|
||||
$ git pull origin
|
||||
// Create a local tracking branch (if you haven't already)
|
||||
|
|
@ -52,62 +49,57 @@ $ git checkout release-9
|
|||
// Merge from master into the branch (this becomes your point in time
|
||||
// from master that you will be releasing from)
|
||||
$ git merge --no-ff master
|
||||
|
||||
|
||||
....
|
||||
|
||||
3. Update the VERSION.txt with changes from the git logs, this populates the resolves issues since the last release.
|
||||
+
|
||||
[source, screen, subs="{sub-order}"]
|
||||
....
|
||||
|
||||
$ mvn -N -Pupdate-version
|
||||
|
||||
|
||||
$ mvn -N -Pupdate-version
|
||||
....
|
||||
|
||||
4. Edit the VERSION.txt file to set the 'Release Version' at the top alongside the Date of this release.
|
||||
+
|
||||
[source, screen, subs="{sub-order}"]
|
||||
....
|
||||
|
||||
$ vi VERSION.txt
|
||||
|
||||
|
||||
$ vi VERSION.txt
|
||||
....
|
||||
|
||||
5. Make sure everything is commit'd and pushed to github.com/eclipse/jetty.project
|
||||
+
|
||||
[source, screen, subs="{sub-order}"]
|
||||
....
|
||||
|
||||
$ git commit -m "Updating VERSION.txt top section" VERSION.txt
|
||||
$ git push origin release-9
|
||||
|
||||
|
||||
$ git push origin release-9
|
||||
....
|
||||
|
||||
6. Prepare the Release
|
||||
+
|
||||
NOTE: This step updates the <version> elements in the pom.xml files, does a test build with these new versions, and then commits the pom.xml changes to your local git repo.
|
||||
____
|
||||
[NOTE]
|
||||
This step updates the <version> elements in the pom.xml files, does a test build with these new versions, and then commits the pom.xml changes to your local git repo.
|
||||
The `eclipse-release` profile is required on the prepare in order to bring in the jetty aggregates as that profile defines a module which is ignored otherwise.
|
||||
____
|
||||
|
||||
+
|
||||
[source, screen, subs="{sub-order}"]
|
||||
....
|
||||
|
||||
$ mvn release:prepare -DreleaseVersion=9.0.0.v20130322 \
|
||||
-DdevelopmentVersion=9.0.1-SNAPSHOT \
|
||||
-Dtag=jetty-9.0.0.v20130322 \
|
||||
-Peclipse-release
|
||||
|
||||
|
||||
-Peclipse-release
|
||||
....
|
||||
7. Perform the Release
|
||||
+
|
||||
NOTE: This step performs the release and deploys it to a oss.sonatype.org staging repository.
|
||||
____
|
||||
[NOTE]
|
||||
This step performs the release and deploys it to a oss.sonatype.org staging repository.
|
||||
____
|
||||
|
||||
+
|
||||
[source, screen, subs="{sub-order}"]
|
||||
....
|
||||
|
||||
$ mvn release:perform
|
||||
|
||||
|
||||
....
|
||||
8. Set up files for next development versions.
|
||||
+
|
||||
|
|
@ -118,15 +110,15 @@ Make sure everything is commit'd and pushed to github.com/eclipse/jetty.project
|
|||
+
|
||||
[source, screen, subs="{sub-order}"]
|
||||
....
|
||||
|
||||
$ vi VERSION.txt
|
||||
$ git commit -m "Updating VERSION.txt top section" VERSION.txt
|
||||
$ git push origin release-9
|
||||
|
||||
|
||||
....
|
||||
|
||||
9. Close the staging repository on oss.sonatype.org
|
||||
|
||||
10. Announce stage to the mailing list for testing.
|
||||
|
||||
11. Once the staged repository has been approved by the rest of the committers.
|
||||
+
|
||||
* Release the staging repository to maven central on oss.sonatype.org
|
||||
|
|
@ -134,12 +126,9 @@ $ git push origin release-9
|
|||
+
|
||||
[source, screen, subs="{sub-order}"]
|
||||
....
|
||||
|
||||
$ git checkout master
|
||||
$ git merge --no-ff release-9
|
||||
$ git push origin master
|
||||
|
||||
|
||||
....
|
||||
|
||||
[[releasing-aggregates]]
|
||||
|
|
@ -153,12 +142,9 @@ To build and deploy the aggregate javadoc and jxr bits:
|
|||
|
||||
[source, screen, subs="{sub-order}"]
|
||||
....
|
||||
|
||||
$ cd target/checkout
|
||||
$ mvn -Paggregate-site javadoc:aggregate jxr:jxr
|
||||
$ mvn -N site:deploy
|
||||
|
||||
|
||||
$ mvn -N site:deploy
|
||||
....
|
||||
|
||||
This will generate the aggregate docs and deploy them to the `/home/www/jetty/<project version>/jetty-project` directory on download.eclipse.org.
|
||||
|
|
@ -181,9 +167,7 @@ Once these are setup you can deploy a release to eclipse with the following inca
|
|||
|
||||
[source, screen, subs="{sub-order}"]
|
||||
....
|
||||
|
||||
$ ./promote-to-eclipse.sh 9.0.0.v20130322
|
||||
|
||||
....
|
||||
|
||||
Each of these scripts will download all of the relevant files from maven central and then copy them into the correct location on eclipse infrastructure.
|
||||
|
|
@ -197,26 +181,20 @@ Maintaining the conventions we use on the site will allow all 'stable' links to
|
|||
|
||||
[source, screen, subs="{sub-order}"]
|
||||
....
|
||||
|
||||
$ ssh <user>@build.eclipse.org
|
||||
$ cd ~downloads/jetty/
|
||||
$ rm -Rf stable-9
|
||||
$ cp -r <version> stable-9
|
||||
$ ./index.sh
|
||||
|
||||
|
||||
$ ./index.sh
|
||||
....
|
||||
|
||||
This needs to be done for all Eclipse Jetty releases (regardless of version). In addition we have to work to reduce the footprint of jetty on the primary eclipse download resources so we want to move older releases to the eclipse archive site.
|
||||
|
||||
[source, screen, subs="{sub-order}"]
|
||||
....
|
||||
|
||||
$ cd ~/downloads/jetty
|
||||
$ mv <old release> /home/data/httpd/archive.eclipse.org/jetty/
|
||||
$ ./index.sh
|
||||
|
||||
|
||||
$ mv <old release> /home/data/httpd/archive.eclipse.org/jetty/
|
||||
$ ./index.sh
|
||||
....
|
||||
|
||||
Periodically we need to do the same for the osgi P2 repositories to keep the size of our downloads directory at a reasonable size.
|
||||
|
|
@ -224,7 +202,7 @@ Periodically we need to do the same for the osgi P2 repositories to keep the siz
|
|||
==== Building an OSGi P2 Repository
|
||||
|
||||
Most of the jetty jars are also osgi bundles, plus we release some specific bundles that link:#framework-jetty-osgi[integrate jetty closely with osgi].
|
||||
To do this, we use a Hudson job on the eclipse infrastructure. You will need to have permission to access https://hudson.eclipse.org/hudson/view/Jetty-RT/
|
||||
To do this, we use a Hudson job on the eclipse infrastructure. You will need to have permission to access https://ci.eclipse.org/shared/view/Jetty-RT/
|
||||
|
||||
There are Hudson jobs that build osgi p2 repos for each of the major releases of jetty:7 (jetty-rt-bundles-7), 8 (jetty-rt-bundles-8) and 9 (jetty-rt-bundles-9).
|
||||
You will need to start a manual build of the job that matches the version of jetty that you are releasing.
|
||||
|
|
|
|||
Loading…
Reference in New Issue