[Kde-extra-gear] String freeze active on extragear ?

Mon Dec 3 22:53:51 CET 2007

<html><head><meta name="qrichtext" content="1" /><style type="text/css">
p, li { white-space: pre-wrap; }
</style></head><body style=" font-family:'Sans Serif'; font-size:10pt; font-
weight:400; font-style:normal;">
Hello, 
OK. So, I'll refrain from 
adding these new strings. In fact, if Ihad to add them, it's because 
kgraphviewer is in final debug mode: I noted that some actions were missing 
whatsthis information. So it'll be for 4.1. It is not a really great problem, 
as I think the actions are easily understandable by themselves.
Bye.
Kleag

On Wednesday 28 November 2007 
08:19:28 Tom Albers wrote:
&gt; Op Tuesday 27 November 
2007 19:46 schreef u:
&gt; &gt; On Tuesday 27 
November 2007, Tom Albers wrote:
&gt; &gt; &gt; Hi,
&gt; &gt; &gt;
&gt; &gt; &gt; As 
kgraphviewer is part of the release project, it should follow the
&gt; &gt; &gt; release 
schedule. So if not strictly needed, I would avoid it.
&gt; &gt;
&gt; &gt; given that it's in 
extragear, this is very much up to the individual
&gt; &gt; developers. the 
problem is, as you note, that if you want to be packaged
&gt; &gt; up with the rest of 
kde during releases, how do we manage that?
&gt; &gt;
&gt; &gt; well, post-4.0 we 
will be providing a "this is what to release" tag for
&gt; &gt; extragear 
developers to use ... so developers can simply tag what is the
&gt; &gt; last stable release 
and continue to develop merily on their own schedule
&gt; &gt; (whatever that may 
be) in trunk/
&gt; &gt;
&gt; &gt; still, requires a 
wee bit of discipline, but not so bad as to tie KEG
&gt; &gt; into the KDE 
release cycle. apps are welcome to follow that release cycle
&gt; &gt; if they wish, 
though, of course =)
&gt;
&gt; Yes, although I agree, 
the subject here was string freeze. So close to a
&gt; release you should not 
change strings unless there are some serious bugs in
&gt; it. But indeed, it's 
your own responsibility.
&gt;
&gt; Toma
</body></html>