NQP's development release cycle is intimately tied to Rakudo's release cycle. There is no separate, independent release cycle for NQP.
Parrot releases the third Tuesday of each month; Rakudo will generally issue its own development release soon after the Parrot release (Usually within a few days). To accomplish this, NQP must be tagged for release immediately prior to the Rakudo release.
Check to see if tools/build/PARROT_REVISION needs to be bumped to a later Parrot release.
If PARROT_REVISION already contains a Parrot release tag (e.g.,
RELEASE_3_9_0) then it does not need to be changed.
If PARROT_REVISION refers to an interim commit,
then update PARROT_REVISION to contain the tag corresponding to Parrot's monthly release.
To see a list of Parrot release tags,
git tag on an up-to-date Parrot repository.
Once tools/build/PARROT_REVISION has been set to a Parrot release, it must not be changed (except to another Parrot release) until after the Rakudo release.
VERSIONfile in nqp:
$ echo '2012.12' > VERSION $ git commit -m 'bump VERSION to 2012.12' VERSION $ git push
$ make realclean $ perl Configure.pl --gen-parrot $ make $ make test
Resolve any problems that may still exist.
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
$ git tag -a -m"tag release YYYY.MM" YYYY.MM # e.g., 2012.12 $ git push --tags