The 3.3 release is coming up in just over two weeks, on 19 April. This is looking to be a smooth, if uneventful, release. Uneventful is good, especially for a supported release.
Call to Arms: 1. I would like to push forward with the whiteknight/imcc_compreg_pmc branch, but I need much more testing before we are confident in merging it. There are a handful of failures for tests like documentation and the test system itself. I don't consider these failures to be so serious as to prevent a merge completely, but they might delay it until after the release. Any tests or help would be much appreciated. 2. Are there any other branches in preparation of being merged? I don't see any that look mature to me, but I might be missing something. Is there anything that is going to be merged this week? Please let me know if we have anything big on the near horizon. 3. Please update NEWS and PLATFORMS. Following a pattern we've been starting in the past few months, we can mention new ecosystem projects, large changes to existing ecosystem projects, changes to Parrot itself, etc. We would like some focus on the parts of Parrot the user will actually see and use, but other accomplishments should be noted as well. 4. We've all got GSoC fever (I'm most guilty of all!), but that shouldn't get in the way of doing proper testing or the other things that need doing. Submit lots of smolder reports! 5. Since this is a supported release, I'm going conservative. We'll do a feature freeze for master on Tuesday 12 April. On that day, I'll put out a fake release or "release candidate" for testing. We've had problems in recent months with installed Parrot causing a variety of problems for projects and on various platforms, so I would like those to be tested and worked out ahead of time. I'll send out an update on 12 April with details. Thanks, --Andrew Whitworth _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
