|
|
To continue the previous email with 3.11 specific information:
Contributing to 3.11 - bug fixes
======================
Follow exactly the same principles as described in the previous email.
Except replace '4.0' with '3.11' in scripts.
additional info:
1) We anticipate having Bob to automatically build and test the sets of
fixes flagged on mantis
2) The fix loading process may be more intelligent, taking account of
dependencies if there are any.
Contributing to 3.11 - Code removal
==========================
1) Make an MC package of the code to be removed.
save that package in the squeaksource/311 repository.
2) Update Sake/Packages with a definition which loads/unloads that package.
(see implementers of #Nebraska for an example).
3) Test using 3.10.2-build, first load the package to perform the
reoganization.
4) unload the package.
5) If it doesn't work simply, any fixes/refactorings required to make it
work should be uploaded to mantis as a changeset/fix to be applied prior
to step 3).
Contributing to 3.11 - Derived Images
===========================
Follow Damien's example as to how he generates the Squeak-dev image. The
package definitions are added to Universes/Sake/Packages. (universes is
more universal, sake/packages is easier to manage).
please do join us on irc #squeak
cheers
Keith
|
Locked
