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. 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? -- View this message in context: http://forum.world.st/About-the-new-release-process-tp4574410p4630175.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.