Well after a long delay we pushed to get 3.10 out the door in a form that would be acceptable to the community. But already issues are turning up. Oh well we would not be the first project to issue a quick .1 'oops' release.
Keith Hodges pointed out a couple of issues on IRC and I created reports for them in the ToDo category on Mantis in the Squeak project. In the Product Version field of each I have chosen 3.10 and either in the summary or description or both I reference a hypothetical 3.10.1. The current issues are http://bugs.squeak.org/view.php?id=7035 http://bugs.squeak.org/view.php?id=7036 You will notice in 7035 that I explicitly request a 3.10.1 by May 26th. I also volunteer to take care of making this happen if you find you can't do it for some reason. I would appreciate hearing the release teams opinion on such a plan by Monday are Tuesday if at all possible (12th and 13th). I chose a date two weeks from Monday to also give us time to collect reports on other annoying but easy to fix issues in 3.10. As I understand there has also been a request for a fuller Welcome with examples of 'cool code'. I've not been following that discussion in detail and so if someone is more familiar with it, please create a ToDo report similar to what I have done above. There have also been calls to release a FunSqueak and relabeling it as Full Squeak. There is no reason of course that it needs to be released on a rush schedule and I suggest basing it on a 'fixed' 3.10.1 rather than the slightly flawed 3.10. Ken
signature.asc
Description: This is a digitally signed message part
_______________________________________________ V3dot10 mailing list [email protected] http://lists.squeakfoundation.org/mailman/listinfo/v3dot10
