From 8a786f4c99c027c518c3a7a59a832433d19e8d7b Mon Sep 17 00:00:00 2001 From: Kevan Benson Date: Mon, 6 Jul 2009 21:10:52 -0700 Subject: [PATCH 1/6] Patch to change bahavior of .push to return modified array, not number of elements Signed-off-by: Moritz Lenz --- src/classes/Array.pir | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/classes/Array.pir b/src/classes/Array.pir index 027ab2c1401..00cadb9a895 100644 --- a/src/classes/Array.pir +++ b/src/classes/Array.pir @@ -175,7 +175,7 @@ Add C to the end of the Array. it_loop_end: $I0 = elements self splice self, args, $I0, 0 - .tailcall self.'elems'() + .return (self) type_error: 'die'('Type check failure in push') .end From 40251e4f9ad04f181e973a98e61d34d1023eb2ed Mon Sep 17 00:00:00 2001 From: Kevan Benson Date: Mon, 6 Jul 2009 21:21:16 -0700 Subject: [PATCH 2/6] Patch to change bahavior of .unshift to return modified array, not number of elements Signed-off-by: Moritz Lenz --- src/classes/Array.pir | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/classes/Array.pir b/src/classes/Array.pir index 00cadb9a895..abfaf6773d3 100644 --- a/src/classes/Array.pir +++ b/src/classes/Array.pir @@ -238,7 +238,7 @@ Adds C to the beginning of the Array. goto it_loop it_loop_end: splice self, args, 0, 0 - .tailcall self.'elems'() + .return (self) type_error: 'die'('Type check failure in push') .end From 0c7475a1134994aaffcea26d1d018b52807e5241 Mon Sep 17 00:00:00 2001 From: Moritz Lenz Date: Tue, 7 Jul 2009 14:39:22 +0200 Subject: [PATCH 3/6] [README] changed some quotes to C<...> POD markup Also changed wording a bit: since I only consider the part in t/spec/ to be the official test suite, we import all of official test suite --- README | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README b/README index 4f4944d74fd..7938bae4768 100644 --- a/README +++ b/README @@ -41,10 +41,10 @@ This will create a "perl6" or "perl6.exe" executable in the current directory. Rakudo doesn't currently have a "make install" target. -The "--gen-parrot" option tells Configure.pl to automatically +The C<--gen-parrot> option tells Configure.pl to automatically download (via 'svn') and build the version of Parrot most appropriate for the copy of Rakudo you currently have. It's -okay to use the --gen-parrot option on later invocations of +okay to use the C<--gen-parrot> option on later invocations of Configure.pl; the configure system will re-build Parrot only if a newer version is needed for whatever version of Rakudo you're working with. @@ -67,13 +67,13 @@ are preserved after they are defined, but variables are not). =head2 Running the test suite -Entering "make test" will run a small test suite that comes +Entering C will run a small test suite that comes bundled with Rakudo. This is a simple suite of tests, designed to make sure that the Rakudo compiler is basically working and that it's capable of running a simple test harness. -Running "make spectest" will import relevant portions -of the official PerlĀ 6 test suite from the Pugs repository +Running C will import the official PerlĀ 6 test suite +from the Pugs repository L and run all of these tests that are currently known to pass. From 19b8db2f544de3961b4a75ebe8ef4d51271d51b6 Mon Sep 17 00:00:00 2001 From: Moritz Lenz Date: Tue, 7 Jul 2009 22:54:48 +0200 Subject: [PATCH 4/6] sync Makefile and release_guide.pod about version formats. Also includes a POD fix. --- build/Makefile.in | 2 +- docs/release_guide.pod | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/build/Makefile.in b/build/Makefile.in index 006e3e870e5..891978f58f6 100644 --- a/build/Makefile.in +++ b/build/Makefile.in @@ -358,7 +358,7 @@ manifest: sort -u -o MANIFEST MANIFEST release: manifest - [ -n "$(VERSION)" ] || ( echo "\nTry 'make release VERSION=yyyymm'\n\n"; exit 1 ) + [ -n "$(VERSION)" ] || ( echo "\nTry 'make release VERSION=YYYY-MM'\n\n"; exit 1 ) [ -d rakudo-$(VERSION) ] || ln -s . rakudo-$(VERSION) $(PERL) -ne 'print "rakudo-$(VERSION)/$$_"' MANIFEST | \ tar -zcv -T - -f rakudo-$(VERSION).tar.gz diff --git a/docs/release_guide.pod b/docs/release_guide.pod index aa25c52e22d..ca3cddc3ba8 100644 --- a/docs/release_guide.pod +++ b/docs/release_guide.pod @@ -134,7 +134,7 @@ Make sure any locally modified files have been pushed back to github. =item 9. -Create an initial tarball by entering "make release VERSION=YYYY-MM", +Create an initial tarball by entering C, where YYYY-MM is the month for which the release is being made. This will create a candidate tarball file named . From 4549f3cee9274406e0d455ea673885ee8d4916b8 Mon Sep 17 00:00:00 2001 From: pmichaud Date: Tue, 7 Jul 2009 18:02:58 -0500 Subject: [PATCH 5/6] Minor update to docs for parrot release number in build/PARROT_REVISION. --- docs/release_guide.pod | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/release_guide.pod b/docs/release_guide.pod index ca3cddc3ba8..b0807b760c4 100644 --- a/docs/release_guide.pod +++ b/docs/release_guide.pod @@ -80,10 +80,11 @@ prior to the release, addressing them as needed. Once Parrot issues its monthly release, edit Rakudo's build/PARROT_REVISION file to contain the subversion revision -number corresponding to Parrot's monthly release. -As always, test to make sure Rakudo still builds and -passes its tests. Once build/PARROT_REVISION has been -set to the Parrot release, it must not be changed until +number and release number corresponding to Parrot's monthly +release. For example, for June 2009 PARROT_REVISION file +contained "39599 1.3.0". As always, test to make sure Rakudo +still builds and passes its tests. Once build/PARROT_REVISION +has been set to the Parrot release, it must not be changed until after the Rakudo release. In other words, we want each monthly release of Rakudo to be able to be built using the immediately prior release of Parrot. From 48c17910660d0aee080e69e061220b410feba7b4 Mon Sep 17 00:00:00 2001 From: pmichaud Date: Tue, 7 Jul 2009 19:04:12 -0500 Subject: [PATCH 6/6] More release_guide.pod improvements. --- docs/release_guide.pod | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/release_guide.pod b/docs/release_guide.pod index b0807b760c4..9c290bdd920 100644 --- a/docs/release_guide.pod +++ b/docs/release_guide.pod @@ -101,6 +101,8 @@ As the actual release date nears, review the git log history to see if any additional items need to be added to the ChangeLog. This can be conveniently done with "git log --since=yyyy-mm-dd --reverse". + $ git commit docs/ChangeLog + =item 5. When it's time to cut the release, create a new release announcement @@ -111,12 +113,17 @@ some small details about the choice of release name. (If the details are a bit lengthy, this can often best be done as a separate section at the bottom of the announcement.) + $ git add docs/announce/YYYY-MM + $ git commit docs + =item 6. Update the release dates and names at the top of this file (docs/release-guide.pod). Also improve these instructions if you find any steps that are missing. + $ git commit docs/release-guide.pod + =item 7. Make sure everything compiles and runs from a known clean state: @@ -128,11 +135,17 @@ Make sure everything compiles and runs from a known clean state: $ make spectest Continue adjusting things until make spectest passes as expected. +Often this means fixing a bug, fudging a test, or removing a +test from t/spectest.data . Use your best judgement or ask others +if uncertain what to do here. =item 8. Make sure any locally modified files have been pushed back to github. + $ git status + $ git push + =item 9. Create an initial tarball by entering C,