1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
|
=head1 release_guide.pod - guide to NQP releases
NQP's development release cycle is intimately tied to Rakudo's release
cycle. There is no separate, independent release cycle for NQP; NQP
must be tagged for release immediately prior to the Rakudo release.
=head2 Steps to create an NQP release
=over 4
=item 1.
MoarVM tries to have a synchronised release schedule with NQP
and Rakudo, so there's most probably a release tag for MoarVM
that you can bump F<tools/templates/MOAR_REVISION> to. Release tags
for MoarVM have the format C<2016.02>. Find all of the tags with
C<git tag> in an up-to-date MoarVM checkout.
=item 2.
Change the C<VERSION> file in nqp:
echo '2016.12' > VERSION
git commit -m 'bump VERSION to 2012.12' VERSION
git push
=item 3.
Make sure everything compiles and runs from a known clean state. This step
is especially important if C<MOAR_REVISION> was changed in step 1 above.
make realclean
perl Configure.pl --gen-moar --backend=moar,jvm
make
make m-test
make j-test
Resolve any problems that may still exist. Issues that impact backends
other than MoarVM may potentially be ignored for a release for now.
Check on the IRC channel if you have any questions.
You will need a JDK (Java Development Kit) installed for building and
running tests for the jvm backend. On Debian, you can install it with:
sudo apt-get install openjdk-11-jdk
=item 4.
Create a release tarball (needed for the Rakudo Star release)
by entering C<make release VERSION=YYYY.MM>, where YYYY.MM is
the month for which the release is being made. This will
create a tarball file named C<nqp-YYYY.MM.tar.gz>.
=item 5.
Unpack the tar file into another area, and test that it
builds and runs properly using the same process in step 3
above. If there are any problems, fix them and go back to
step 3.
=item 6.
Tag NQP by its release month ("YYYY.MM")
git tag -u <email address> -s -a -m "tag release YYYY.MM" YYYY.MM # e.g., 2016.12
git push --tags
The C<-s> tells git to sign the tag with your GPG key. Please see Rakudo's
release guide for links on how to create GPG keys and upload them to GitHub,
should it be necessary.
=item 7.
Sign the tarball:
gpg -b --armor nqp-YYYY.MM.tar.gz
=item 8
Upload the release tarball and signature to L<http://rakudo.org/downloads/nqp>:
scp nqp-2013.12.tar.gz nqp-2013.12.tar.gz.asc \
rakudo@rakudo.org:public_html/downloads/nqp/
If you do not have permissions for that, ask one of (pmichaud, jnthn, FROGGS,
masak, tadzik, moritz, PerlJam/perlpilot, [Coke], lizmat, timotimo, fsergot,
hoelzro, Zoffix) on #raku or #raku-dev to do it for you.
=item 9.
If creating the NQP release as part of a Rakudo release,
continue with the Rakudo release process.
=back
|
