Is it time to initiate the next release project?
***
In response to: The Weekly Juan #10: "Cheap, High Quality Fonts in Squeak" stephane ducasse stephane.ducasse at free.fr Tue May 1 20:36:14 UTC 2007 wrote:
are you planning to produce a package that can be loaded in 3.9 or 3.10?
Stef
***
Which was a perfectly good question to ask Juan.
Regardless of Juan's response a few other questions need to be asked.
1) Would this addition be appropriate within the current scope of 3dot10's mission?
2) Is the board ready to look beyond the 3dot10 release project and initiate the 3dot11 project?
Regardless of the answer to 1. there will be other tantalizing improvements and enhancements proposed now that will only be appropriate for the next release cycle. How are those to be handled?
It seems to me we are cutting ourselves off at the knees by looking no farther than the current release project. It puts unfair forces on the project to increase its scope. We will burn out our self funded volunteers.
To have things happen, resources must be found and allocated. And the project beyond 3dot10 deserves to have some consideration and planning starting NOW. And we need to board to give its offical consederation to the next step in the journey. (Because that step will need the board's blessing.)
Thank you for your consideration of these matters.
Yours in curiosity and service, --Jerome Peace
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
- Would this addition be appropriate within the
current scope of 3dot10's mission?
I terms of 3.10's mission, this addition, if it is possible to package this up as an additional load in a package to 3.10, then it falls outside of 3.10's mission, and into 3.10's package universe.
best regards
Keith
Yes, because 3.10 is due to end soon, and there ought to be a plan about what to do after that.
-Ralph
Il giorno mar, 01/05/2007 alle 22.47 -0500, Ralph Johnson ha scritto:
Yes, because 3.10 is due to end soon, and there ought to be a plan about what to do after that.
And there ought to be a plan about what to do after "after that", too. In other words, we need a roadmap.
Oh, and a stable release team (one that doesn't change after every release) wouldn't be bad, too ;-)
Giovanni
squeak-dev@lists.squeakfoundation.org