Marcus Denker wrote:
On 28.09.2008, at 22:16, Keith Hodges wrote:
considering that mantis now has >1000 open entries...
Marcus
??
The difference being, that we dont create a mantis entry so that it can languish unused. We use mantis as a vessel for holding snippets of code and collecting feedback.
Installer collects a list of fixes applied, and Sake/Tasks has a task for documenting those fixes in the image.
So fixes are not integrated into the image anymore and the report then closed?
When a release image is released the fixes are integrated into the image as normal, and can be closed or marked "fixed". Everything that I have been developing loads into "all" existing images, so for example, LPF may want to load fixes into 3.7 if it needs something. Previously fixes are ONLY available by waiting for the release team to harvest, or by manually loading a changeset in yourself. Now the harvesters can make a fix readily available for everyone through Installer. This attitude of supporting all users of squeak, while moving things forward for everyone, is a core-value of the 3.11 team.
What I don't understand with the use of Installer with mantis entries: From my experience from 3.6 to 3.9, there is quite some dependency between fixes. Nothing is automatic, if you or some script loads the wrong fix in the wrong order then that is a problem. Thas means: two fixes are overriding the same method, to harvest both, the second one applied can not be added but needs to be redone to take the changes of the first into account.
I really can't imagine how you can automatically apply changesets from the bugtracker Nothing is automatic.
to build "your own release". This just can't work with all the dependencies between fixes. However, the old way, fixes are applied to a moving target, since the alpha image is continuously being updated. With this approach fixes applied to 3.10 (a fixed target) are used to create a 3.11 unstable until the combination of fixes is deemed "stable"
Keith