1 Removals 2 KCP 3 MCP 4 Anthony runtime enhancements (split in two - fixes and closures) 5 Craig's simulator fixes 6 mir Network rewrite 7 TrueTypeTextStyle 8 Diego look style enhancements 9 Replace fonts with AccuFonts (mainly in order to remove the old - people can now load additional nice fonts themselves anyway). 10 SM 1.1 11 Inclusion of SM plus related packages in the release image (though maintained as packages, not directly by update stream).
Here's our current 3.6 plan list of larger enhancements/tasks. Right now, we have 4 1/2 of these done... maybe we'll get a couple more in before the end of the week. They've been moving along somewhat slowly for various reasons.
For larger enhancements, specifically these ones singled out for the 3.6 release, I wonder if it would help to assign a guide or harvester as a "shepherd" for each one. Someone who would be responsible for tracking progress on the enhancement and deciding when enough review has happened and when it's ready to go in. Right now, there's not really anyone responsible for most of these, so it sort of falls to me to make sure something happens, or a random person complaining on one of the mailing lists. I don't really have time to handle all of these myself.
I remember Goran hinted at something like this with his PROP proposal or whatever it was. But just something simple like assigning people to shepherd these items might help things get done.
Does this make sense?
- Doug
Just wanted to make a few comments in the midst of the all the heat and smoke, but no _anger_. :)
Like many I am for the Squeak which can be anything you want it to be. Server Squeak, Multimedia Squeak, OS Environment Squeak.
I really like the TTF and New Look stuff. I would really like the visual aspects of Squeak to be polished and shine, shine, shine. :)
I understand those who want to honor the _Date_ committment. I understand those who want to honor a _Feature_ committment. I agree. :)
I would like to encourage those who may be discouraged because of a perception of slow progress. The perception of their goodies possibly (but hopefully will now) not getting in due only becoming available just prior to the _Date_.
Understand that the process is not mature. The tools are not mature.
Much of the time during this _alpha_ period have been without Marcus as Harvestor and without BFAV.
From my perception the BFAV is enabling more people to step up to the plate and contribute. As the tools and _process_ improve more people will likely join in to help as the time committment might not be as high.
We have much to be encouraged about. Please, please be encouraged and not discouraged. The good things will make it into Squeak (via SM or image). And please feel free to define what you call _good things_.
I don't believe that the Guides/Community choosing to either continue forward with 3.6 and _Date_ or delay the _Date_ to help the _Features_ with hurt Squeak or the community.
We need to allow the Guides and the Community and the Process to mature the Process for all of us to fully grasp it.
So whether the _Date_ is strictly adhered to or if a small 1-2 week delay is introduced, we need to understand it doesn't make any of this a normative part of the _Process_. It won't break anything. These are growing pains. Be of good cheer. That is a good thing. It means progress.
So please cheer up. We have much to be thankful for and much to look forward to.
Jimmie Houchin Squeak Cheerleader RA RA SHISH BOOM BA. ;) (ahhhh! now I've shouted. :)
Proverbs 17:22 A merry heart does good like a medicine: but a broken spirit dries up the bones.
squeakfoundation@lists.squeakfoundation.org