(DISCLAIMER, opinions are my personal ones and not coordinated with SHR people yet)
Raster has fixed the "e eats CPU cycles" bug, so the current unstable should be much nicer from now on. Thanks raster!.
Indeed it is such a nice improvement that I propose to move the current -unstable to -testing, freeze it and only fix bugs until we are happy with it. This could be a good candidate for the first stable SHR milestone. But this is just my personal opinion, what do people think about it?
I have started a draft release note page in the wiki:
draft release notes that could describe the new -testing (and later -stable) snapshot. Feel free to expand and correct the page.
Ainulindale, do you agree such a plan would be good/feasible? If we make the transition from -unstable to -testing now, we could bake it for some time and during the FSOSHRUDCON'09 you could announce the release of the first -stable milestone ;-).
feedback/input welcome.
spaetz
Raster has fixed the "e eats CPU cycles" bug, so the current unstable should be much nicer from now on. Thanks raster!.
Indeed it is such a nice improvement that I propose to move the current -unstable to -testing, freeze it and only fix bugs until we are happy with it. This could be a good candidate for the first stable SHR milestone. But this is just my personal opinion, what do people think about it?
I have started a draft release note page in the wiki:
draft release notes that could describe the new -testing (and later -stable) snapshot. Feel free to expand and correct the page.
Ainulindale, do you agree such a plan would be good/feasible? If we make the transition from -unstable to -testing now, we could bake it for some time and during the FSOSHRUDCON'09 you could announce the release of the first -stable milestone ;-).
feedback/input welcome.
spaetz
Leave a comment