| 1 |
Instructions for Apache-Reload Release Manager |
| 2 |
|
| 3 |
0. Ask the PMC to verify that you have the appropriate CPAN permissions |
| 4 |
on dev@perl. |
| 5 |
|
| 6 |
If this is your first release, ask someone with APML karma on PAUSE |
| 7 |
to verify you have the appropriate permissions. Likely someone on |
| 8 |
the PMC can do this. |
| 9 |
|
| 10 |
a. login into https://pause.perl.org |
| 11 |
b. menu click: Select Mailinglist/Action |
| 12 |
c. choose APML and Change Permissions and click go |
| 13 |
d. click 3.1 Make somebody else co-maintainer |
| 14 |
e. choose the modules to give the perms to |
| 15 |
type the username of the new co-maintainer |
| 16 |
f. if you happen to know that packages were added this release, |
| 17 |
make sure you give the correct permissions to them. |
| 18 |
% MAINTAINER_BUILDING_RELEASE=1 perl Makefile.PL |
| 19 |
|
| 20 |
1. 'make disttest' - to make sure nothing is missing from the manifest. |
| 21 |
Now 'make dist', and test this generated package (not svn) |
| 22 |
with as many configurations as possible on as many platforms |
| 23 |
as possible. |
| 24 |
|
| 25 |
a. edit ./Changes: |
| 26 |
- change -dev to -rc\d+ starting with -rc1 |
| 27 |
|
| 28 |
b. commit Changes |
| 29 |
% svn ci -m "0.14 rc1" Changes |
| 30 |
|
| 31 |
c. nuke any preinstalled Apache-Reload libs and run 'make test' |
| 32 |
|
| 33 |
d. test that you can 'make install' and then run 'make test' again |
| 34 |
|
| 35 |
e. test whether we are still 100% OK on systems with no LWP: |
| 36 |
% APACHE_TEST_PRETEND_NO_LWP=1 make test |
| 37 |
|
| 38 |
2. once confident that the package is good, commit the release candidate |
| 39 |
to https://dist.apache.org/repos/dist/dev/perl and post 24 hour-ish |
| 40 |
candidate alert to the various lists |
| 41 |
|
| 42 |
o dev/perl.apache.org |
| 43 |
o modperl/perl.apache.org |
| 44 |
|
| 45 |
(or maybe longer to give most people a chance to catch up). no need |
| 46 |
to tag this package |
| 47 |
|
| 48 |
Subject: [RELEASE CANDIDATE] Apache-Reload 0.14 RC\d+ |
| 49 |
|
| 50 |
a. if problems are detected during stage 2, repeat stages 1 and 2. |
| 51 |
|
| 52 |
3. when the package has been reported to be good, prepare a new |
| 53 |
package to be released |
| 54 |
|
| 55 |
a. edit ./Changes |
| 56 |
- remove -rc\d+ |
| 57 |
- add release date |
| 58 |
|
| 59 |
b. rerun: |
| 60 |
% perl Makefile.PL |
| 61 |
make sure tag looks right |
| 62 |
% make -n tag |
| 63 |
|
| 64 |
c. commit Changes |
| 65 |
% svn ci -m "0.14 release" Changes |
| 66 |
|
| 67 |
d. tag |
| 68 |
% make tag |
| 69 |
|
| 70 |
e. create the final package |
| 71 |
% make dist |
| 72 |
|
| 73 |
f. test the final package again at least once |
| 74 |
|
| 75 |
4. Upload the package to CPAN |
| 76 |
|
| 77 |
5. Announce the package |
| 78 |
|
| 79 |
a. post to the following list: |
| 80 |
|
| 81 |
o modperl/perl.apache.org |
| 82 |
|
| 83 |
Subject: [ANNOUNCE] Apache-Reload 0.14 |
| 84 |
|
| 85 |
include: |
| 86 |
- MD5 sig (as it comes from CPAN upload announce). |
| 87 |
- the latest Changes |
| 88 |
|
| 89 |
6. Prepare for the next cycle |
| 90 |
|
| 91 |
a. increment version in lib/Apache/Reload.pm and lib/Apache2/Reload.pm also |
| 92 |
|
| 93 |
b. edit ./Changes: |
| 94 |
- start a new item with incremented version + '-dev' |
| 95 |
|
| 96 |
=item 0.15-dev |
| 97 |
|
| 98 |
c. bump up version numbers in this file to make it easier to do the |
| 99 |
next release. |
| 100 |
% perl -pi.bak -e 's/(\d+)\.(\d+)/join(".", $1, $2+1)/eg' RELEASE |
| 101 |
|
| 102 |
(undo the change to the PAUSE menu item number in item 0d. above) |
| 103 |
|
| 104 |
d. commit Changes |
| 105 |
% svn ci -m "start 0.14-dev cycle" Changes RELEASE \ |
| 106 |
lib/Apache/Reload.pm lib/Apache2/Reload.pm |