Hi, On May 14, 2012, at 8:45 PM, Sean P. DeNigris wrote:
> > EstebanLM wrote >> >> our new release process... >> two bug fix releases at month 4 and month 8... >> During this year we'll also release bugfix versions of Pharo 1.4. >> > > This is exciting because as soon as a version is released, everyone starts > pounding on it and inevitably finding bugs. It will be nice to have those > fixes go into the current version instead of instantly starting to focus on > the next major version months or a year away. yep... that's the idea... :) > I noticed bug issues relevant to 1.4 getting tagged with 2.0 milestone. How > do we get fixes into the 1.4 bug release versions? If we make a slice off > the 1.4 package, there may be many conflicts merging into 2.0, but if we > merge in the future version, there will be many 2.0-only changes that have > nothing to do with the fix, won't there? What's the protocol? And now that > we're time-based, what's the date for the first bug fix release? relevant issues for 1.4 are tagged now 2.0/1.4... some others just 1.4 (not many). What we considered non-relevant were re-tagged just 2.0... maybe we made a mistake in our review, but we are willing to retag them if someone has other feelings :) now... the slices can be applied in both versions or be version specific... the bugtracker keeps the information needed to the integration. times, times... we still didn't thought on times for versions release for 1.4 because we are still adjusting all to the process... but I think some time on july is good for first 1.4 release and maybe october for lastest... in any case, we are doing regular 1.4 integrations (weekly), that incorporates some bugfixes. best, Esteban
