Hello All,
The first result of the 3.11 effort is going to be an image that I have called 3.10bc. Where bc stands for "Build Candidate". The purpose of this image is to provide a base starting point for everyone who would like to contribute to 3.11, and do image building activities of any kind. 3.10bc is the first "fixed point", being essentially the stable 3.10 release, against which small projects can be carried out safely. To if you were to test a bug fix, and I want to reproduce it, it will be a case of taking 3.10bc and repeating your test. 3.10bc consists of, 3.10.2 + LevelPlayingField (Monticello, PackageInfo, MonticelloConfigurations, Monticello-Files, Installer-Launcher), and the latest of AtomicLoading, Universes, SqueakMap, Sake/Packages, SUnit, and Tasks, together with some essential fixes which support the above packages. Full details of the mantis bug reports for those fixes are included in the image. This "base" is generated and should be easily reproducible for any of the images supported by LevelPlayingField. Some tools like SUnitGUI are not backwardly compatible, BUT SUnit includes a non GUI TestReporter which is. Projects which can start based upon 3.10bc A) Bug Harvesting All the outstanding bugs on mantis can be assessed, in their respective categories. B) Image Tidying C) Image wide adjustments renaming etc. e.g. _ to := revisited. == to = Transcript show -> self logCR: D) Module Definition and Removal Move classes into a category, make them into a monticello package, move methods to become extension methods, and publish the package. E) Validation of external packages, and getting more stuff to work And many more I am sure. 3.10bc+fixes, from A above, will be a continuously moving target, for those intending to build on top of 3.11, so instead we provide a 3.11bc this will be 3.10bc + tidying, reorg and removals. But Not Bug Fixes. This is an image that may be used as a second fixed point if preferred. back to the day job for a few days for me I am afraid Keith |
Hi Keith -
Not sure where to report this but I noticed that this fix is not in yet and it will definitely cause problems: Installer mantis bug: 6980 fix: 'SystemDictionary-recreateSpecialObjectsArray-M6980.st'. Is there a procedure for proposing fixes for inclusion? (this is why I was interested in a wiki - I could've added that and you'd have a place to go to the next round) Cheers, - Andreas Keith Hodges wrote: > Hello All, > > The first result of the 3.11 effort is going to be an image that I have > called 3.10bc. Where bc stands for "Build Candidate". > > The purpose of this image is to provide a base starting point for > everyone who would like to contribute to 3.11, and do image building > activities of any kind. > > 3.10bc is the first "fixed point", being essentially the stable 3.10 > release, against which small projects can be carried out safely. > > To if you were to test a bug fix, and I want to reproduce it, it will be > a case of taking 3.10bc and repeating your test. > > 3.10bc consists of, 3.10.2 + LevelPlayingField > (Monticello, PackageInfo, MonticelloConfigurations, Monticello-Files, > Installer-Launcher), and the latest of AtomicLoading, Universes, > SqueakMap, Sake/Packages, SUnit, and Tasks, together with some essential > fixes which support the above packages. Full details of the mantis bug > reports for those fixes are included in the image. > > This "base" is generated and should be easily reproducible for any of > the images supported by LevelPlayingField. Some tools like SUnitGUI are > not backwardly compatible, BUT SUnit includes a non GUI TestReporter > which is. > > Projects which can start based upon 3.10bc > > A) Bug Harvesting > > All the outstanding bugs on mantis can be assessed, in their respective > categories. > > B) Image Tidying > > C) Image wide adjustments renaming etc. > > e.g. > > _ to := revisited. == to = Transcript show -> self logCR: > > D) Module Definition and Removal > > Move classes into a category, make them into a monticello package, move > methods to become extension methods, and publish the package. > > E) Validation of external packages, and getting more stuff to work > > And many more I am sure. > > 3.10bc+fixes, from A above, will be a continuously moving target, for > those intending to build on top of 3.11, so instead we provide a 3.11bc > this will be 3.10bc + tidying, reorg and removals. But Not Bug Fixes. > This is an image that may be used as a second fixed point if preferred. > > back to the day job for a few days for me I am afraid > > Keith > > > > > > > |
Andreas Raab wrote:
> Hi Keith - > > Not sure where to report this but I noticed that this fix is not in > yet and it will definitely cause problems: > > Installer mantis bug: 6980 fix: > 'SystemDictionary-recreateSpecialObjectsArray-M6980.st'. > > Is there a procedure for proposing fixes for inclusion? (this is why I > was interested in a wiki - I could've added that and you'd have a > place to go to the next round) We left the wiki behind for editing tasks via monticello. Over 90 fixes have been added this way by various contributors. In this case the task would be: Squeak310MakeBuildCandidate-#taskEssentialFixes In the near future I am aiming to enable a fix to be included simply by switching the "Status" in Mantis. I have been discussing with Ken about adding two further status' to mantis. One for placing it into the unstable build and one for placing it in the stable build. We havent decided on the appropriate wording. In the meantime, I started experimenting with using "Acknowledged" status for unstable and "Confirmed" for stable (since these status levels are all but unused at present" Keith |
Free forum by Nabble | Edit this page |