Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Commit metadata for 4.4.0, Parrot Banana Fanna Fo Ferret.

  • Loading branch information...
commit 210ad264c4e3e2da03209f71c11ce2817b895f91 1 parent d6dfa2e
@Whiteknight Whiteknight authored
View
3  CREDITS
@@ -112,9 +112,10 @@ D: typo squisher
E: yDNA@cpan.org
N: Andrew Whitworth
+D: Product Manager (2.9.0 - current)
D: Internals development
D: Documentation
-D: Release manager for 0.8.2, 1.3.0, 1.5.0, 2.4.0, 2.11.0, 3.3.0, 3.10.0 and 4.0.0
+D: Release manager for 0.8.2, 1.3.0, 1.5.0, 2.4.0, 2.11.0, 3.3.0, 3.10.0, 4.0.0 and 4.4.0
E: wknight8111@gmail.com
U: Whiteknight
View
6 ChangeLog
@@ -1,3 +1,9 @@
+2012-06-XX release 4.5.0
+ - Core
+ - Documentation
+ - Tests
+ - Community
+
2012-05-15 release 4.4.0
- Core
+ Most internal calls to libc exit(x) have been replaced with
View
6 MANIFEST.generated
@@ -1,14 +1,14 @@
# See tools/dev/install_files.pl for documentation on the
# format of this file.
# Please re-sort this file after *EVERY* modification
-blib/lib/libparrot.4.3.0.dylib [main]lib
+blib/lib/libparrot.4.4.0.dylib [main]lib
blib/lib/libparrot.a [main]lib
blib/lib/libparrot.dylib [main]lib
blib/lib/libparrot.so [main]lib
-blib/lib/libparrot.so.4.3.0 [main]lib
+blib/lib/libparrot.so.4.4.0 [main]lib
compilers/data_json/data_json.pbc [data_json]
config/gen/call_list/opengl.in []
-cygparrot-4.3.0.dll [main]bin
+cygparrot-4.4.0.dll [main]bin
docs/ops/bit.pod [doc]
docs/ops/cmp.pod [doc]
docs/ops/core.pod [doc]
View
2  README.pod
@@ -4,7 +4,7 @@
=head1 NAME
-README.pod - Readme to Parrot, version 4.3.0.
+README.pod - Readme to Parrot, version 4.4.0.
=head1 DESCRIPTION
View
2  VERSION
@@ -1 +1 @@
-4.3.0
+4.4.0
View
1  docs/parrothist.pod
@@ -142,5 +142,6 @@ Starred release numbers indicate supported releases.
dukeleto 4.2.0 2012-Mar-20 "Ornithopter"
cotto 4.3.0 * 2012-Apr-17 "In Which..."
+ Whiteknight 4.4.0 2012-May-15 "Banana Fanna Fo Ferret"
=cut
View
94 docs/project/release_manager_guide.pod
@@ -2,16 +2,18 @@
=head1 RELEASE MANAGER GUIDE
-This guide lays out, in detail, the steps necessary to prepare, to assemble,
-and to publish a parrot release. Please ensure you carefully follow each
-step in the process, and, as always, if you have any questions, please ask.
+This guide lays out in detail the steps necessary to prepare, assemble
+and publish a Parrot release. Please ensure you carefully follow each
+step in the process. As always, please ask for help if you need it.
NOTE: You can use the newish/experimental script auto_release.pl to automate
much of his guide (up to section IX):
perl tool/release/auto_release.pl X.Y.Z
-Run perldoc on the tool to get more documentation.
+Run perldoc on the tool to get more documentation. This tool is new and
+experimental. Your mileage may vary. Be prepared to do things manually if you
+have problems with this script.
=head2 I. Preparations During the Month Before a Release
@@ -36,7 +38,7 @@ log of these meetings at L<http://irclog.perlgeek.de/parrotsketch/>.
=item 3
A couple of weeks in advance of the release, ask people to run C<make fulltest>
-and report (and hopefully fix!) any problems they discover. Check-in with
+and report (and hopefully fix!) any problems they discover. Check-in with
language project leaders (I<e.g.,> Rakudo) for any potential release blockers.
This will, hopefully, afford them sufficient time apply any fixes. Also,
please ask people to review any issues targeted for the upcoming release at
@@ -45,23 +47,23 @@ L<https://github.com/parrot/parrot/issues>.
=item 4
During the course of the release process, you will need to be able to log in
-and operate on two different servers. To oversimplify a bit, you will need to
+and operate on two different servers. To oversimplify a bit, you will need to
be able to execute these two commands and their C<scp> equivalents.
=over 4
=item * C<ssh parrot@ftp-osl.osuosl.org>
-In order to do this, please ensure your public SSH key(s) have been added to
+In order to do this, please ensure your public SSH key(s) have been added to
the FTP server L<ftp-osl.osuosl.org>. You can open a support ticket for this by
-sending an email to C<support@osuosl.org> with your public SSH keys as
+sending an email to C<support@osuosl.org> with your public SSH keys as
attachments. Without them, you will not be able to ship the release.
=item * C<ssh E<lt>usernameE<gt>@parrot.org>
-Also, set up your account on L<http://parrot.org/>. Any previous release
-manager should be able to help you, but you may also need to open a support
-ticket at C<support@osuosl.org> in order to be added to the C<parrot> group.
+Also, set up your account on L<http://parrot.org/>. Any previous release
+manager should be able to help you, but you may also need to open a support
+ticket at C<support@osuosl.org> in order to be added to the C<parrot> group.
The C<parrot> group has permissions to create the new directories necessary to
contain documentation for new releases.
@@ -71,7 +73,7 @@ contain documentation for new releases.
A couple of days in advance, announce the new release to
C<parrot-dev@lists.parrot.org> and to the IRC channel C<#parrot>. Ask whether
-there are any showstopping bugs. Check-in again with the language project
+there are any showstopping bugs. Check-in again with the language project
leads. It's also good to ask for updates to
L<http://github.com/parrot/parrot/blob/master/ChangeLog>,
L<http://github.com/parrot/parrot/blob/master/CREDITS>,
@@ -83,14 +85,14 @@ and L<https://github.com/parrot/parrot/wiki/Languages>.
=item 6
On the Saturday before the release, you should notify other developers to stop
-committing non-release related code to the master branch. This will help to
-avoid complications. They are, of course, free to commit to branches as much
+committing non-release related code to the master branch. This will help to
+avoid complications. They are, of course, free to commit to branches as much
as they want. You may also set the topic in C<#parrot>, announcing the
time you plan to start the release procedure. This will aid the committers.
=item 7
-You may also select a name (and optionally a quote) for your release. For
+You may also select a name (and optionally a quote) for your release. For
example, you could select a name from
L<http://en.wikipedia.org/wiki/List_of_parrots>.
@@ -103,18 +105,18 @@ subsequent steps.
=head2 II. Get the Most Recent Changes
-The day of the release has arrived. Please ensure you have checked out the most
+The day of the release has arrived. Please ensure you have checked out the most
recent version of the master branch:
git checkout master
git pull --rebase
-Also, ensure you do not have any local commits which have not yet been pushed
+Also, ensure you do not have any local commits which have not yet been pushed
and thoroughly tested. You can do so with the following command:
git log origin/master..
-If this produces no output, then your local master and the remote master are
+If this produces no output, then your local master and the remote master are
in sync.
=head2 III. Update the Release Version
@@ -127,11 +129,11 @@ version-specific information.
=over 4
-=item 1.
+=item 1.
=over 4
-=item a.
+=item a.
Use C<tools/release/update_version.pl> to update the version string in several
files. For example,
@@ -143,11 +145,11 @@ F<tools/release/update_version.pl> invalidates any existing generated bytecode.
Assuming you ran it in a directory with an existing build, you must now
run C<make reconfig> to clear out any invalid bytecode.
-=item b.
+=item b.
Update the version number, the date, and your name in L<http://github.com/parrot/parrot/blob/master/docs/parrothist.pod>.
-=item c.
+=item c.
Update this file
(L<http://github.com/parrot/parrot/blob/master/docs/project/release_manager_guide.pod>)
@@ -170,8 +172,8 @@ day of the release.
=item 3
-Update release-related information in F<tools/release/release.json>. You will
-use this later for the release announcements. There are a few, essential
+Update release-related information in F<tools/release/release.json>. You will
+use this later for the release announcements. There are a few, essential
fields which must be updated at each release:
=over 4
@@ -215,12 +217,12 @@ if there have been no new entries to F<PBC_COMPAT>.
If this is a supported release and new entries to F<PBC_COMPAT> have been
added since the last supported release, add a new entry with a new major
-version number for this release at the top of the list. For example,
+version number for this release at the top of the list. For example,
3.0 2007.10.17 coke released 0.4.17
Delete all minor version numbers since the last major bytecode version number,
-as these are used only in development and are not relevant to the bytecode
+as these are used only in development and are not relevant to the bytecode
support policy. Those changes are all included within the major version number
increase for the supported release.
@@ -282,17 +284,17 @@ using C<make release> or using C<make release_check>.
=over 4
-=item a.
+=item a.
Begin by running:
make release VERSION=a.b.c
-where a.b.c is the version number (I<e.g.,> C<3.8.0>). This will create the
-tarball named F<parrot-a.b.c.tar.gz>. The F<DEVELOPING> file is automatically
+where a.b.c is the version number (I<e.g.,> C<3.8.0>). This will create the
+tarball named F<parrot-a.b.c.tar.gz>. The F<DEVELOPING> file is automatically
excluded from the release tarball.
-=item b.
+=item b.
Extract F<parrot-a.b.c.tar.gz> into another directory:
@@ -300,7 +302,7 @@ Extract F<parrot-a.b.c.tar.gz> into another directory:
cd ~/another/directory
tar -xvzf parrot-a.b.c.tar.gz
-=item c.
+=item c.
Verify that the build process runs smoothly:
@@ -323,7 +325,7 @@ into a temporary directory, and then reconfigure, rebuild, re-test
=back
-Whichever of these two approaches you use, verify the version is correct and
+Whichever of these two approaches you use, verify the version is correct and
B<does not> contain the suffix C<devel>:
./parrot -V
@@ -384,12 +386,12 @@ part easier. You can specify the format of your announcements like so,
./parrot tools/release/crow.pir --type=html
Copy the output and paste it into the application you need. HTML works well for
-Perl and PerlMonks and text works well for the rest. It's a good idea (although
+Perl and PerlMonks and text works well for the rest. It's a good idea (although
not necessary) to add a "highlights" section to draw attention to major new
-features. If you do, be sure to say the same thing in both the text and the
+features. If you do, be sure to say the same thing in both the text and the
HTML versions.
-Please ensure you include the SHA256 sums of the tarballs in the release
+Please ensure you include the SHA256 sums of the tarballs in the release
announcement which are automatically generated by C<make release>.
=head2 IX. Update the Website
@@ -438,11 +440,11 @@ on which type of release this is.
Update L<http://docs.parrot.org>. Run C<make html> in a release copy of Parrot,
and save the F<resources/> and F<html/> directories created in F<docs/>. Use
SSH to login to L<< <username>@parrot.org >> and expand these into a release
-directory (e.g. 3.8.0) in the webroot (I<i.e.,>
-F</var/www/docs.parrot.org/htdocs/parrot>) for L<http://docs.parrot.org>. In
-C<< <webroot>/parrot >>, there are symbolic links for C<latest>, C<supported>,
-and C<devel>. Update the C<latest> symlink to point to your new directory. If
-this is a supported release, also update the C<supported> symlink. Do not
+directory (e.g. 3.8.0) in the webroot (I<i.e.,>
+F</var/www/docs.parrot.org/htdocs/parrot>) for L<http://docs.parrot.org>. In
+C<< <webroot>/parrot >>, there are symbolic links for C<latest>, C<supported>,
+and C<devel>. Update the C<latest> symlink to point to your new directory. If
+this is a supported release, also update the C<supported> symlink. Do not
delete any old copies of the docs and don't update the other symlinks.
=item 7
@@ -457,7 +459,7 @@ to keep the main page fresh.
=head2 X. Update parrot.github.com and the Relevant parrot-docsx Repository
To update both the C<parrot.github.com> and the relevant C<parrot-docsx> repositories,
-execute the following command:
+execute the following command:
perl tools/release/parrot_github_release.pl
@@ -465,7 +467,7 @@ Please note: To review the available options, use the C<-h | --help> option.
In addition, you may also want to review the pod with,
C<perldoc tools/release/parrot_github_release.pl>.
-For more information about the update process, I<see>
+For more information about the update process, I<see>
L<http://github.com/parrot/parrot/blob/master/docs/project/release_parrot_github_guide.pod>.
=head2 XI. Publicity
@@ -491,8 +493,8 @@ client lets you.
Modify the topic on C<#parrot>, for example,
- /topic #parrot Parrot 4.0.0 "[Name of Parrot Release]" |
- http://parrot.org/ | Log: http://irclog.perlgeek.de/parrot |
+ /topic #parrot Parrot 4.0.0 "[Name of Parrot Release]" |
+ http://parrot.org/ | Log: http://irclog.perlgeek.de/parrot |
#parrotsketch meeting Tuesday 19:30 UTC
=item 4
@@ -532,14 +534,14 @@ The calendar of releases is available at the C<comp.lang.parrot> Google
calendar, visible at
L<http://www.google.com/calendar/render?cid=ldhctdamsgfg5a1cord52po9h8@group.calendar.google.com>.
- - May 15, 2012 - 4.4.0 - whiteknight
- - Jun 19, 2012 - 4.5.0 - alvis
+ - Jun 19, 2012 - 4.5.0 - alvis
- Jul 17, 2012 - 4.6.0 - ??
- Aug 21, 2012 - 4.7.0 - ??
- Sep 18, 2012 - 4.8.0 - ??
- Oct 16, 2012 - 4.9.0 - dukeleto
- Nov 20, 2012 - 4.10.0 - ??
- Dec 18, 2012 - 4.11.0 - ??
+
=cut
__END__
View
2  include/parrot/oplib/core_ops.h
@@ -19,7 +19,7 @@
#include "parrot/runcore_api.h"
PARROT_EXPORT
-op_lib_t *Parrot_DynOp_core_4_3_0(PARROT_INTERP, long init);
+op_lib_t *Parrot_DynOp_core_4_4_0(PARROT_INTERP, long init);
opcode_t * Parrot_end(opcode_t *, PARROT_INTERP);
opcode_t * Parrot_noop(opcode_t *, PARROT_INTERP);
View
6 src/ops/core_ops.c
@@ -24444,7 +24444,7 @@ op_lib_t core_op_lib = {
PARROT_FUNCTION_CORE, /* core_type = PARROT_XX_CORE */
0, /* flags */
4, /* major_version */
- 3, /* minor_version */
+ 4, /* minor_version */
0, /* patch_version */
1125, /* op_count */
core_op_info_table, /* op_info_table */
@@ -24573,7 +24573,7 @@ static void hop_deinit(PARROT_INTERP)
hop_buckets = NULL;
}PARROT_EXPORT
op_lib_t *
-Parrot_DynOp_core_4_3_0(PARROT_INTERP, long init) {
+Parrot_DynOp_core_4_4_0(PARROT_INTERP, long init) {
/* initialize and return op_lib ptr */
if (init == 1) {
@@ -24602,7 +24602,7 @@ Parrot_lib_core_ops_load(PARROT_INTERP)
{
PMC *const lib = Parrot_pmc_new(interp, enum_class_ParrotLibrary);
- ((Parrot_ParrotLibrary_attributes*)PMC_data(lib))->oplib_init = (void *) Parrot_DynOp_core_4_3_0;
+ ((Parrot_ParrotLibrary_attributes*)PMC_data(lib))->oplib_init = (void *) Parrot_DynOp_core_4_4_0;
dynop_register(interp, lib);
return lib;
}
View
13 tools/release/release.json
@@ -1,9 +1,8 @@
{
- "release.version" : "4.3.0",
- "release.name" : "In Which...",
+ "release.version" : "4.4.0",
+ "release.name" : "Banana Fanna Fo Ferret",
"release.day" : "Tuesday",
- "release.nextdate" : "17 April 2012",
- "release.nextdate" : "15 May 2012",
+ "release.nextdate" : "19 June 2012",
"web.root" : "http://parrot.org/",
"web.source" : "download",
@@ -12,10 +11,10 @@
"web.org_root" : "https://github.com/parrot",
"bugday.day" : "Saturday",
- "bugday.date" : "13 May 2012",
+ "bugday.date" : "16 June 2012",
"wiki.root" : "https://github.com/parrot/parrot/wiki",
- "wiki.bugday" : "bug_day_2012_03_17",
+ "wiki.bugday" : "bug_day_2012_06_16",
- "ftp.path" : "ftp://ftp.parrot.org/pub/parrot/releases/stable/4.3.0/"
+ "ftp.path" : "ftp://ftp.parrot.org/pub/parrot/releases/stable/4.4.0/"
}
Please sign in to comment.
Something went wrong with that request. Please try again.