June 7, 2012
12:50 p.m.
Stéphane Ducasse wrote: > + 1 > Marcus can you add it to the pharo-project web site. > > >>> no new bugs tagged 1.4 are important ones for the incremental release. >>> We will not maintain two versions in parallel. Just **important** = show stopper fixes. >>> >> Especially as one Person's enhancement is the other persons bug... any large change >> will have side effects, so we should really limit us a bit. >> >> -> No new features. >> -> No cleanups >> -> If a bug was there in Pharo 1.1 already and we lived with it for years, fixing it in >> the current dev version is (in many cases) enough. >> (There are exceptions, but is does not happen often). >> -> Community input is important. A ready-to-include fix with a description that it >> was tested and a note that it for sure works will not be ignored. >> For an entry that is nearly finished yet nobody even cares to test it, why bother? >> Just a random idea... that perhaps the issue tracker tags and templates could be updated to advise of this philosophy. * Remove template "Pharo 1.4 Enhancement". * Template "Pharo 1.4 Bug" currently has an empty description. Include Steph's description above - particularly the bit about recording which Pharo version a fix has been tested on.. The template label might be changed from "Milestone-1.4" to "Maintenance-1.4" - since that milestone has already passed. cheers, Ben >> The best thing is to just do it. The list is here: >> >> http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D1.4 >> >> Marcus >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> >> > > > >