Pre-3.6 code freeze
Will Coleda
will at coleda.com
Mon Jul 18 21:30:21 UTC 2011
On Mon, Jul 18, 2011 at 10:40 AM, Will Coleda <will at coleda.com> wrote:
> On Thu, Jul 14, 2011 at 10:38 PM, James E Keenan <jkeen at verizon.net> wrote:
>> We are now in a code freeze prior to this coming Tuesday's release of Parrot
>> 3.6.
>>
>> Please conduct any and all work on source code in branches rather than in
>> master. If you feel that your work ought to be merged in to master before
>> the release, please test your branch thoroughly on multiple OSes and submit
>> a git pull request.
>>
>> But, with the exception of patches which reduce the number of failing tests
>> on Win32, our preference will be to defer any merges into master until after
>> the release on Tuesday.
>>
>> What do we need between now and the release?
>>
>> * Patches that reduce the number of failing tests on Windows.
>>
>> * Smoke tests on Linux, FreeBSD, OpenBSD, Darwin, Win32.
>>
>> * Build HLLs and run their tests on top of Parrot master. Feedback on
>> Rakudo Perl 6 on top of Parrot is particularly welcome.
>>
>> Thank you very much.
>>
>> kid51
>>
>> _______________________________________________
>> http://lists.parrot.org/mailman/listinfo/parrot-dev
>>
>
> It would also be nice to get updates to PLATFORMS. I just updated the
> win7 entry (Thanks to Notfound and Whiteknight for investigating and
> patching that platform), and removed all the 2009-vintage build
> information, which doesn't leave us with much.
Thanks to notfound, whiteknight, and benabik, I now have a 100%-pass
on windows 7.
http://smolder.parrot.org/app/projects/report_details/18152
(PLATFORMS updated)
If you already had a windows checkout on this file, and the test
doesn't pass after your next pull, let us know on #parrot.
--
Will "Coke" Coleda
More information about the parrot-dev
mailing list