From kde-release-team Mon Dec 03 14:18:58 2007 From: Allen Winter Date: Mon, 03 Dec 2007 14:18:58 +0000 To: kde-release-team Subject: Re: Does the string freeze remain in effect? Message-Id: <200712030919.00012.winter () kde ! org> X-MARC-Message: https://marc.info/?l=kde-release-team&m=119669157907550 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============0862775054==" --===============0862775054== Content-Type: multipart/alternative; charset="iso-8859-6"; boundary="Boundary-00=_TBBVHCgFacIYQw2" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-00=_TBBVHCgFacIYQw2 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit On Sunday 02 December 2007 11:02:58 Thomas Friedrichsmeier wrote: > Hi, > > ok, so KDE 4.0 has been delayed by around a month. Does this open another > window to do some string changes (if so, for how long), or does the string > freeze remain in effect? > All freezes (API, feature, string) remain in effect until trunk is open for 4.1 development. > On a more general note: I suppose for people who are highly involved in kde > development this will not be a problem, and the information is accessible > somewhere, but as an on-and-off contributor, I've found myself confused about > what is or is not allowed at the moment, more than once. To me it would be > really helpful, if there was a large visible note right at the top of > http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule (or some other > highly visible page), which always lists the freezes which are currently in > effect, and how long they are expected to stay in effect. > I'll see what I can do. -Allen --Boundary-00=_TBBVHCgFacIYQw2 Content-Type: text/html; charset="iso-8859-6" Content-Transfer-Encoding: 7bit

On Sunday 02 December 2007 11:02:58 Thomas Friedrichsmeier wrote:

> Hi,

>

> ok, so KDE 4.0 has been delayed by around a month. Does this open another

> window to do some string changes (if so, for how long), or does the string

> freeze remain in effect?

>

All freezes (API, feature, string) remain in effect until trunk is open for 4.1 development.

> On a more general note: I suppose for people who are highly involved in kde

> development this will not be a problem, and the information is accessible

> somewhere, but as an on-and-off contributor, I've found myself confused about

> what is or is not allowed at the moment, more than once. To me it would be

> really helpful, if there was a large visible note right at the top of

> http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule (or some other

> highly visible page), which always lists the freezes which are currently in

> effect, and how long they are expected to stay in effect.

>

I'll see what I can do.

-Allen

--Boundary-00=_TBBVHCgFacIYQw2-- --===============0862775054== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team --===============0862775054==--