-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nils Kneuper schrieb:
| Looks like my other mail was lost, so here again the remainder about the
deadline:
|
| | * deadline for 1.4.0 commits: Sunday, 2nd March, 1pm (gmt+1)
|
| That is ~11h from now. Commit your stuff that is meant to get into
I think we should shorten our stable-release interval to 6 months.
This is not a conclusion I have arrived at casually or quickly. I've
been observing this project for nine months now. I think it suffers
from some of the well-known problems associated with long release
intervals, including (1)
Mark de Wever [EMAIL PROTECTED]:
I do get the impression the rate of reported bugs is increasing
and I expect quite some bugs to be discovered in 1.4.
That being said; I do like to get and keep the bug count low but I think
it will be hard.
I'm a little more optimistic, which is
Mark de Wever [EMAIL PROTECTED]:
On Sun, Mar 02, 2008 at 09:06:48AM -0500, Eric S. Raymond wrote:
I think we should shorten our stable-release interval to 6 months.
Personally I think the current cycle of about one year is rather nice. A
release costs quite some resources for final
On Sun, Mar 02, 2008 at 11:22:29AM -0500, Eric S. Raymond wrote:
Mark de Wever [EMAIL PROTECTED]:
On Sun, Mar 02, 2008 at 09:06:48AM -0500, Eric S. Raymond wrote:
I think we should shorten our stable-release interval to 6 months.
Personally I think the current cycle of about one year is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nils Kneuper schrieb:
| * deadline for 1.4.0 commits: Sunday, 2nd March, 1pm (gmt+1)
Turns run out!
| * trunk frozen + start of release stuff: Sunday, 2nd March, 2pm (gmt+1)
Turns run out!
| * trunk free for 1.4+1.5 commits (not branched off yet):
Benoit Timbert [EMAIL PROTECTED]:
In fact, unlike 1.2 and 1.0, none of our translation teams could manage to get
100% of the strings translated.
Maybe with a shorter cycle we'll have less strings will be added/changed so it
would be easier to finish the translation.
Btw i thing this problem
ott [EMAIL PROTECTED]:
So if short release cycles mean
lots of campaign churn, expect reduced translation activity.
I don't think these two things are coupled. For one thing, I think
most of the campaign churn we're going to see in the foreseeable
future has already
Am Sonntag 02 März 2008 schrieb Nils Kneuper:
And one requirement before anything gets lifted from now on is 2 complete
months with the *revised* texts in wescamp. I do not want to see such
Just to make sure...
1. WesCamp-i18n is currently not supported well by g.w.o ...
2. Developing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nils Kneuper schrieb:
| Nils Kneuper schrieb:
| | * deadline for 1.4.0 commits: Sunday, 2nd March, 1pm (gmt+1)
|
| Turns run out!
|
| | * trunk frozen + start of release stuff: Sunday, 2nd March, 2pm (gmt+1)
|
| Turns run out!
|
| | * trunk free for
Nils Kneuper [EMAIL PROTECTED]:
And one requirement before anything gets lifted from now on is 2
complete months with the *revised* texts in wescamp. I do not want
to see such excessive stringchanges to happen again when the content
is already in mainline.
Fair enough.
--
a
This is a basic idea tought on the fly.
1) Any mainline content is a no-go zone for translators for the first
half of the development cycle. That is you can translate things, but
they might get changed and reverted at any moment due to various reasons.
2) At the half point campaign
12 matches
Mail list logo
