Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Branch: master
Fetching contributors…

Cannot retrieve contributors at this time

102 lines (74 sloc) 3.476 kB
{
"text.news" : true,
"text.text" : "
On behalf of the Parrot team, I'm proud to announce Parrot @release.version@, also known
as \"@release.name@\". Parrot (@web.root@) is a virtual machine aimed
at running all dynamic languages.
Parrot @release.version@ is available on Parrot's FTP site
(@ftp.path@), or by following the
download instructions at @web.root@@web.source@. For those who would like
to develop on Parrot, or help develop Parrot itself, we recommend using Git to
retrieve the source code to get the latest and best Parrot code.
Parrot @release.version@ News:
@NEWS@
The SHA256 message digests for the downloadable tarballs are:
@message_digests@
Many thanks to all our contributors for making this possible, and our sponsors
for supporting this project. Our next scheduled release is at @release.nextdate@.
Enjoy!
",
"html.news" : true,
"html.text" : "
<p>On behalf of the Parrot team, I'm proud to announce Parrot @release.version@,
also known as &quot;@release.name@&quot;. <a href=\"@web.root@\">Parrot</a>
is a virtual machine aimed at running all dynamic languages.</p>
<p>Parrot @release.version@ is available on <a href=\"@ftp.path@\">Parrot's FTP
site</a>, or by <a href=\"@web.root@@web.source@\">following the download
instructions</a>. For those who want to hack on Parrot or languages that run on top of Parrot,
we recommend <a href=\"@web.org_root@\">our organization page</a> on GitHub,
or you can go directly to the official Parrot Git repo on <a href=\"@web.repository@\">Github</a>
To clone the Parrot Git repo into a directory called 'parrot', use the following:
<pre>
git clone git://github.com/parrot/parrot.git
</pre>
If you want it to be in a directory other than 'parrot', then just give that as a second
argument to clone:
<pre>
git clone git://github.com/parrot/parrot.git parrot_foo
</pre>
<p>Parrot @release.version@ News:<br/>
<pre>@NEWS@</pre></p>
<p>The SHA256 message digests for the downloadable tarballs are:</p>
<pre>@message_digests@
</pre>
<p>Thanks to all our contributors for making this possible, and our sponsors
for supporting this project. Our next scheduled release is at @release.nextdate@.</p>
<p>Enjoy!</p>
",
"bugday.news" : false,
"bugday.text" : "
Bug Day
On @bugday.day@, @bugday.date@, please join us on IRC in #parrot
(irc://irc.parrot.org/#parrot) to work on closing out as many tickets
(https://github.com/parrot/parrot/issues) as possible in the parrot queue. This will
help us get ready for the next release of parrot: @release.version@, scheduled
for @release.day@, @release.date@. You'll find C, parrot assembly, perl,
documentation, and plenty of tasks to go around. Core developers will be
available most of the day (starting at around 10am GMT) to answer questions.
No experience with parrot necessary.
--From: @wiki.root@@wiki.bugday@--
Check the list at:
https://github.com/parrot/parrot/milestones/@release.version@
Which contains all the tickets I'd like to see resolved in @release.version@. To
see all the open tickets, use:
https://github.com/parrot/parrot/issues
If you've got something you're working on that you think you'll be
getting done before the release, please
- add a ticket for it (if necessary);
- set its milestone to this release.
Thanks in advance for your patches and commits. ^_^
... Speaking of patches, we should also get through as many of these
(accept or reject) as possible.
@web.root@@web.openpatches@
"
}
Jump to Line
Something went wrong with that request. Please try again.