On Nov 4, 2009, at 11:04 AM, mhanwell@gmail.com wrote:
New extensions introduce new strings, and break any notion of a string
freeze to improve translation coverage.
The string freeze for 1.0 is definitely more like a “slush.” Well
beyond the date of the string freeze, there were any number of changes
which broke strings. And many of the bug-fixes for translations have
made minor breaks in the strings as well. Case in point, several UI
files were not properly translated, resulting in “untranslatable”
strings.
translators get time to work on it. There are numerous examples of
projects that support i18n and freeze their strings.
That’s true. But as a project, we have not been good about such things
for 1.0. I’m sure we’ll get better over time, but there were ~20 new
strings right before the release. So as the person handling
translations, I don’t see the level of commitment you suggest. Adding
plugins doesn’t affect the core code or the library.
There seems to be consensus behind a policy of 1.0.x introduces
nothing new. That’s fine, although I suggest we then remove the z-
matrix editor, since it is currently disabled by default and broken.
I’m happy to let Cryos strike the cartesian editor from the 1.0.x
branch for now, in favor of trunk.
Again, what is wrong with an unstable release series or nightly builds
that track head development.
I have nothing against it. I’d be happy to have nightly builds of both
stable and development trees. I’m already doing 1.0.x builds for Mac.
I would hope we could get some nightly Windows builds going.
But in all the previous discussions about releases and stable
branches, there was also no mention of a timeline. I think it’s
important that we can say “OK, the new cartesian editor will be
available in 1.2, which should be released in the Spring.” Otherwise,
it’s very frustrating – we’ve been in a development model where new
features are added each release, and now suddenly that appears to stop.
So I think it’s really important to make some timelines:
- We’re going to focus hard on bug-fixes and documentation for the
near future, for 1.0.1 and 1.0.2. New contributions will go into trunk. - We’ll open up a 1.1 development series in December, with an estimate
on a new stable 1.2 release sometime in the summer of 2010. - Contributed plugins should go here for people to find and/or install.
Again, if you look at projects like KDE or even GCC, there’s a clear
timeline for contributors.
Just my $0.02.
-Geoff