blob: 32c937ae93c35830aaae2580e6c50dd70f5c2e22 [file] [log] [blame]
Pierre De Rop3a00a212015-03-01 09:27:46 +00001
2
3
4Apache Felix Dependency Manager Release Guide
5This document describes how to do a source release. It is based on the Release FAQ [1]
6
7Prerequisites
8=============
9
10To create a release you must:
11
12* Have Subversion installed on your system;
13* Have gpg installed on your system;
14* Have a public key added to the keys file, and committed to [2]
15* If you are using an http proxy, configure the following:
16
17 export GRADLE_OPTS="-Dhttps.proxyHost=www.somehost.org -Dhttps.proxyPort=8080"
18
19Before you can start staging a release candidate, you must:
20
21* make sure there are no dependencies on snapshots/unreleased versions;
Pierre De Rop6501bac2015-06-11 22:41:04 +000022* increment the ext.dmRelease parameter in release/build.gradle, if not already done, and commit.
23* check if release notes are up-to-date, in release/resources/changelog.txt
24* under bndtools, release (only) the bundles that needs to be released (using "Release workspace bundles" menu).
Pierre De Rop3a00a212015-03-01 09:27:46 +000025* create a tagged version of the sources in preparation of the release candidate.
26
Pierre De Rop6501bac2015-06-11 22:41:04 +000027Realease only the necessary bundles
28===================================
29
30Click on the bndtools "Release workspace bundles", and release the bundles that have been modified and need to be released.
31Don't release other unmodified bundles.
32Once done, under the shell prompt, svn remove the previous old released bundles, svn add the new released bundles,
33refresh the repositories under bndtools, and commit.
34
35Create a tagged version
36=======================
37
Pierre De Rop3a00a212015-03-01 09:27:46 +000038Creating a tagged version of the sources can be done directly through svn (replace r<n> by the actual release number, like "r1"):
39
40svn copy https://svn.apache.org/repos/asf/felix/trunk/dependencymanager https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.dependencymanager-r<n> -m "Release of Apache Felix Dependency Manager r<n>"
41
42Staging a release candidate
43===========================
44
45Staging a release starts by checking out a tagged version of the sources (replace r<n> by the actual release number, like "r1"):
46
47svn co https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.dependencymanager-r<n>
48
49The next step is to build/test the software and create the release/staging/ directory (where the source/jars will be packaged):
50(replace r<n> by the actual release number, like "r1")
51
52Use a Java7 JDK
53
54$ cd org.apache.felix.dependencymanager-r<n>
55$ ./gradlew rat
56$ ./gradlew org.apache.felix.dependencymanager.annotation:jar
57$ ./gradlew jar
58$ ./gradlew test
59$ ./gradlew check
60
Pierre De Ropa20b7582015-03-05 07:30:49 +000061create the staging:
Pierre De Rop3a00a212015-03-01 09:27:46 +000062
63$ ./gradlew makeStaging (this will create ./release/staging/ directory)
64
65Then you sign archives by invoking the following task:
66
67$ ./gradlew signStaging
68
69You can upload the archives and the signatures to our development area, which we use to stage this release candidate. This development area can be found at
70https://dist.apache.org/repos/dist/dev/felix and adding files to it can be done using "svnpubsub" which is taken care of by the following target:
71
72$ ./gradlew commitToStaging
73
74Voting on the release
75=====================
76
77Start a vote on the dev@felix.apache.org list, for example (be sure to replace r<n> with the correct release number, like "r1"):
78
79>>>
80To: "Felix Developers List" <dev@felix.apache.org>
81Subject: [VOTE] Release of Apache Felix Dependency Manager release r<n>
82
83Hi,
84
85We solved N issues in this release:
86http://issues.apache.org/jira/...
87
88There are still some outstanding issues:
89http://issues.apache.org/jira/...
90
91Staging repository:
92https://dist.apache.org/repos/dist/dev/felix/apache-felix-dependencymanager-r<n>/
93
94You can use this UNIX script to download the release and verify the signatures:
95http://svn.apache.org/repos/asf/felix/trunk/dependencymanager/release/check_staged_release.sh
96
97Usage:
98sh check_staged_release.sh r<n> /tmp/felix-staging
99
100This script, unlike the original Felix check_stage_release.sh, will download staging from https://dist.apache.org/repos/dist/dev/felix instead of
101http://repository.apache.org/content/repositories.
102
103
104Please vote to approve this release:
105
106[ ] +1 Approve the release
107[ ] -1 Veto the release (please provide specific comments)
108
109This vote will be open for 72 hours.
110<<<
111
112Promoting the release:
113=====================
114
115Move the artifacts from the development area to the final release location at
116https://dist.apache.org/repos/dist/release/felix by invoking the following target:
117
118$ ./gradlew promoteToRelease
119
Pierre De Ropa20b7582015-03-05 07:30:49 +0000120Then Edit the ./release/build.gradle script, increment the "ext.dmRelease" property, and commit.
121
Pierre De Rop3a00a212015-03-01 09:27:46 +0000122Cancelling the release
123======================
124
125$ ./gradlew deleteFromStaging
126
127[1] http://www.apache.org/dev/release.html
128[2] http://www.apache.org/dist/felix/KEYS