FAQ: How do fixes and enhancements become updates?
Last updated at 7:22 pm UTC on 7 April 2003
This question is answered in some detail on the Harvesting Process page.
More specific questions and answers:
- How and when does a [FIX] or [ENH] from the Squeak Mailing Lists get to the update stream?
- The Harvesting Process is handled by a group called The Harvesters. In short: Sometimes the [FIX] is modified, extended, or done in a different manner before being released (if the [FIX] is actually just fixing a symptom of the real problem, The Harvesters will normally ignore the patch and do the real fix). All fixes will eventually go by Doug Way for at least a brief final QC (quality check) before being released as an [UPDATE]. (See Code updates)
- How and when does an [UPDATE] from the updates server get created?
- Since Squeak 3.4, all [UPDATE]s originate from selected [GOODIE]s, [ANN]s, [FIX]s, and [ENH]s sent to the Squeak Mailing Lists and reviewed by The Harvesters. Whether a [FIX] or [ENH] sent to the list becomes an [UPDATE] depends on a number of things – here the update collector (harvester) applies their experience and judgement to make the decision. Sometimes one person's [ENH] is another's [YUCK!]. ;-)
- How and when does an [UPDATE] from the Squeak Mailing Lists get put on the updates server?
- All [UPDATE]s are issued by Doug Way and announced on the list.
- Does an 'official' Squeak image include all changes on the change server which were added before the release date?
- Yes, but the changes file is normally condensed for each "official" version release, so previous versions of methods will be lost. A full sequential update from way back will retain the previous versions of everything in the changes file.
See also:
Reporting Bugs and Fixes and Stefan Matthias Aust's comments on bug/fix reporting.
Modifications to this page:
