[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Again, msg not translated in KDE 2.1
From:       David Faure <david () mandrakesoft ! com>
Date:       2001-02-25 15:32:33
[Download RAW message or body]

On Saturday 24 February 2001 20:29, Wolfram Diestel wrote:
> Je Sabato, la 24a de Februaro 2001 11:34, David Faure skribis:
> 
> > It has been a bit messy, with many repackaging already at the beginning of
> > the week, and this commit went in unintentionnally. I apologize for that,
> > but it's too late now.
> 
> I would suggest a longer time between tagging and packaging for the next
> major release.

This would mean even more "moving the tag" mess. Probably not a very
good idea.

> This would give all the people with CVS access the ability 
> to checkout the tagged version and test the code and translations some days
> before the packages are made. 

This is exactly what was supposed to happen between the "hard freeze" date
and the tagging date. But it didn't happen this way, because too much bugfixing
still has happened in the last days. Tagging before might be an incentive for
making less changes after the tagging, but that's not even sure (look at
what happened this time).

> Moving the tag by hand (by one responsible 
> person) for every bug fix will ensure that messages aren't changed by them.

But this is exactly what broke this time. After Matthias' insistence on that,
nobody except the release dude moves the tag. But that's exactly
what created the problem: I moved the tag on all of kicker because I thought 
that only multihead-fixes had happened there - and I caught the i18n change 
by mistake because of that. So maybe it would be better if the developer who 
makes a fix would move the tag and then tell me about it - provided that
the commit has been approved first, of course (by me or by kde-core-devel).

> kde-i18n should be tagged just before the packaging so the translators can
> use these last days to improve theire translations. But you have to ensure,
> that the mergescripts work with the tagged version until kde-i18n is tagged
> too.
> Comments?
This last bit makes it all very difficult. I don't have access to the i18n 
merging scripts (Stephan has) - so it would require quite some coordination 
to get this right, potentially for not much result... If the "hard freeze" had been
more respected, there wouldn't be a need for this.

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://perso.mandrakesoft.com/~david/, http://www.konqueror.org/
KDE, Making The Future of Computing Available Today

[prev in list] [next in list] [prev in thread] [next in thread]