The next release 0.4.4 will be prepared this weekend. The usual terms
apply:
- no more feature changes to Parrot core
- docu updates, trivial bug fixes, ..., welcome
- as well as updates to PLATFORMS, smoke reports, test results
Thanks,
leo
The next release will be rolled out this weekend. The usual terms apply:
* no feature changes to Parrot core incl. build
* bug and docu fixes welcome
leo
Garrett Goebel <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch wrote:
>>
>> WRT release name: Piers has proposed "The Leaping Kakapo"
>> (whatever that is:) We could also name it "The Leaping
>> Aoudad".
> A Kakapo is a flightless night parrot: http://www.kakapo.net/en/. So leaping
> Kakapo does make
Leopold Toetsch wrote:
>
> WRT release name: Piers has proposed "The Leaping Kakapo"
> (whatever that is:) We could also name it "The Leaping
> Aoudad".
A Kakapo is a flightless night parrot: http://www.kakapo.net/en/. So leaping
Kakapo does make a kind of sense. "kaka" is the Maori word for par
You knew it already, but just to make sure ...
- No new feature checkins
- Object patches are fine
- Tests, bug fixes, docu updates, and such are more then welcome
Release date is still considered to be Feb, 29th.
*If* objects need some more days to settle, release will be on Feb, 30th
(that is th
>cvs server: sticky tag `HEAD' for file `classes/timer.pmc' is
>not a branch
do
$ cvs update -A classes/timer.pmc
to remove the "sticky tag" and try committing again.
The sticky tag gets set when cvs checkout/update is done with
the -r option.
>leo
HTH,
arvindh.
This e-mail and any fi
Melvin Smith <[EMAIL PROTECTED]> wrote:
> cvs checkout -r imcc1final parrot
I don't know, if this is related, but I get now errors on commit:
cvs server: sticky tag `HEAD' for file `classes/timer.pmc' is not a branch
I did commit some patches an hour before which worked fine. Now I
suddenly get
At 01:08 PM 1/15/2004 -0500, Dan Sugalski wrote:
At 11:05 AM +0100 1/15/04, Leopold Toetsch wrote:
Melvin Smith wrote:
Feel free to checkout branch imcc1final to test with.
Could you be a bit more verbose about that. I've now checked out the
branch "imcc1final", which switched the whole tree to u
At 1:17 PM -0500 1/15/04, Melvin Smith wrote:
At 10:27 AM 1/15/2004 -0500, Melvin Smith wrote:
At 11:05 AM 1/15/2004 +0100, Leopold Toetsch wrote:
Melvin Smith wrote:
Feel free to checkout branch imcc1final to test with.
The command should be:
cvs checkout -r imcc1final parrot
Could you be a bit m
At 10:27 AM 1/15/2004 -0500, Melvin Smith wrote:
At 11:05 AM 1/15/2004 +0100, Leopold Toetsch wrote:
Melvin Smith wrote:
Feel free to checkout branch imcc1final to test with.
The command should be:
cvs checkout -r imcc1final parrot
Could you be a bit more verbose about that. I've now checked out t
At 11:05 AM +0100 1/15/04, Leopold Toetsch wrote:
Melvin Smith wrote:
Feel free to checkout branch imcc1final to test with.
The command should be:
cvs checkout -r imcc1final parrot
Could you be a bit more verbose about that. I've now checked out the
branch "imcc1final", which switched the whole
At 04:17 PM 1/15/2004 +, Jonathan Worthington wrote:
From: "Melvin Smith" <[EMAIL PROTECTED]>
> I'd like to get imcc1 working as correct as possible and frozen
> within a couple of weeks, then I'll start on the really major rework
> for imcc2 (including all the deprecation that is going to mak
From: "Melvin Smith" <[EMAIL PROTECTED]>
> I'd like to get imcc1 working as correct as possible and frozen
> within a couple of weeks, then I'll start on the really major rework
> for imcc2 (including all the deprecation that is going to make everyone
> mad at me.) ;)
Any chance of a list of wha
At 10:28 AM 1/15/2004 +, you wrote:
On Thu, Jan 15, 2004 at 02:21:56AM -0500, Melvin Smith wrote:
> I'd like to get imcc1 working as correct as possible and frozen
> within a couple of weeks, then I'll start on the really major rework
> for imcc2 (including all the deprecation that is going to
At 11:05 AM 1/15/2004 +0100, Leopold Toetsch wrote:
Melvin Smith wrote:
Feel free to checkout branch imcc1final to test with.
The command should be:
cvs checkout -r imcc1final parrot
Could you be a bit more verbose about that. I've now checked out the branch
I would not checkout the branch into th
Melvin Smith wrote:
Feel free to checkout branch imcc1final to test with.
The command should be:
cvs checkout -r imcc1final parrot
Could you be a bit more verbose about that. I've now checked out the
branch "imcc1final", which switched the whole tree to use that sticky
tag. Into which branch
I'm freezing imcc as version 1 except for bug fixes.
I'm working on fixing the PCC code emitter before
freezing it.
Besides the bugs concerning non-scalability of the register
allocator, I'm interested in any bug reports (for IMCC only) that may
have been Warnocked until now.
I'd like to get imcc1
justifies a
release.
* Feature freeze is from now Oct, 29th 8.00 GMT until
* Code freeze starts at Oct, 31th 8.00 GMT
During feature freeze, only core patches WRT building, testing,
warnings, bug fixes and the like should go in (languages/* aren't affected).
leo
[1]
- The Big Move: Parr
--- Steve Fink <[EMAIL PROTECTED]> wrote:
>The code name is, of course,
> open for discussion. Although I reserve the right to call it the
> "hairy tulip" release if I want.
>
"Hairy tulip" is shorter than "open for discussion"
http://home.pyramid.net/gallery/hairytulip.jpg
You can call me anyth
Had to stick that year on in case this message gets unearthed.
Ok, the little voices in my head have told me that it's time for that
release we were talking about. So, you have until Sunday to cram in
any functionality you want in the next release. After Sunday, it will
be cleanups, bugfixes, and
I think I've finally straightened my mail configuration out enough for
this to go somewhere. There is no feature freeze. That was just an old
message that was dug up accidentally from the past. I denied it
several times as soon as I saw it, which wasn't very soon because I
recently had
Steve Fink wrote:
As for the code name -- I'm personally leaning towards the "Juice"
suggestion. I'm not sure why, but it just sounds kinda cool. And it
does fit well with the -Oj flag. "Parrot -- now with extra juice!" Or
something. Opinions?
Too much honor ;)
What about one of these:
http://
Steve Fink wrote:
> [...] does fit well with the -Oj flag. "Parrot -- now with extra juice!"
-Oj Simpson?
"Parrot -- now get away with murder!" :-)
A
Steve Fink wrote:
> As for the code name -- I'm personally leaning towards
> the "Juice" suggestion.
Given that Juice is already the name of an existing (but apparently defunct)
virtual machine, you might want to consider another choice. The home page
appears dead:
http://www.ics.uci.edu/
This is a day late, but as previously announced, Parrot is now
feature-frozen. I'll cut a release next Saturday, March 15, unless
things look good enough to go before then.
"Feature freeze" means bugfixes and new tests are still ok.
The only currently in-progress feature that I
In message <[EMAIL PROTECTED]>
Simon Cozens <[EMAIL PROTECTED]> wrote:
> So, if you're running on one of the core platforms, please check out a
> *clean* CVS copy, try and build and post the output of make test.
Tests cleanly on linux/x86:
perl t/harness
t/op/basic..ok, 1/2 skippe
26 matches
Mail list logo