On Jun 7, 2012, at 9:03 AM, Stéphane Ducasse wrote:
On Jun 7, 2012, at 6:11 AM, Sean P. DeNigris wrote:
I want to backport some fixes from 2.0 into 1.4. What's the best way to do that?
Also, it seems to me that, given our new development process, all bugs should be tagged for both 1.4 and 2.0 unless they specifically don't apply to 1.4â¦
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? 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