In line with my attitude that the main Strawberry "product" should be conservative, reliable and predictable (I'm going with a rough analogy to Firefox product-wise) I've been thinking a little about how the release tempo should look.
My current thinking for Strawberry Perl is to do quarterly releases, with a tentative schedule of releases in January/April/July/October and aiming at being available for download before the second Monday of the month.
This will loosely break down to three month-long phases per release.
A month to review the fallout from the previous release, and experiment with new things and decide what should go into the next release.
A month to get the new stuff implemented, ditch the stuff we can't get done, feature freeze and release a beta, and then a month to do the beta-testing, bug fix and give plenty of warning time for anything that needs the stuff in the new release to preview it.
So in line with this schedule, I'd like to hear from people on features that you'd like to see in the April release. The following is my current list.
Features Being Added Already
- A "real" Perl::Dist and Perl::Dist::Strawberry release with proper documentation
- Simultaneous building of multiple versions (Perl 5.8.8 and Perl 5.10.0)
- libwin32 installed by default (based on feedback from cpan.strawberryperl.com download logs)
- Expat and XML::Parser installed by default.
- Auto-upgrading toolchain for CPAN.pm (configure_requires support)
- Standardised build process for C libraries (libgmp accidentally had SSE2 compiled in which broke on some Athlon systems)
- All bundled modules updated to the latest non-broken release.
Features That Won't Be Considered (Probably)
- "Official" Vista Support (upstream C toolchain issues not fully resolved yet)
- Installation to places other than C:\strawberry (non-trivial config and makefile issues stll)
- Availability as an
If you want any additions considered beyond this set, speak now.
Discussion welcome in irc.perl.org #win32.