Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: D. Michael McIntyre <rosegarden.trumpeter@gm...> - 2008-11-03 19:17:58
We have another good but small batch of crash fixes and repairs to broken
features, and activity has dwindled to a point where I think now is a good
time to go ahead and begin the process of rolling out another release. I
hope this will be the last release of the KDE/Qt3 line of code, because we
are already looking at more of a merge problem than I would like to face when
it comes time to shift everything over to the new Qt4 line permanently, but
we will have to see how everything goes from here. This line is not dead,
because there is nothing to replace it yet, so there may well be a 1.7.4 and
beyond, as events unfold from here.
We're going back to working from the stable_1_7 branch for this one, so those
of you with commit access, please commit any changes to that branch if you
would be so kind. The rest of you should work with .po files from the stable
branch if at all possible (I'll even email them to you if you can't be
bothered to check out a copy of the branch,) because it will save me the step
of having to merge .po files from some other branch into this tree, which
requires needless extra work to keep everything cross-synchronized.
There is very little new work to do for this translation. Most of you just
have an opportunity to catch up what wasn't ready for the last few releases.
Everyone should try to take a look, as one of these new strings will be
visible to everyone.
I'm planning to start the release push one week from now, which doesn't give
any of you much time to work. If anyone really wants to get some translation
work done but needs more time, speak up. I don't expect the pre- and
release-candidate process to take very long for this release, because the
code that has changed has been well-tested in the course of working out how
to fix these problems, and the only truly new feature has actually been
around and in the field since this point in the process of releasing 1.7.2,
when a feature came in just a day too late to make it into that release. As
such, we'll probably have only one week of pre- and release-candidate
opportunity before the final release goes out, or a total of two weeks from
now until the release is official. That's the plan at this point anyway.
Thanks for your continuing efforts to make Rosegarden one of the most
widely-translated music applications out there!
D. Michael McIntyre