Howdy, According to the milestones [1] we are currently in a message freeze. Obviously that needs to be changed. When would be a good time to have the message freeze? After the second beta (25 Aug)? After the first release candidate? What release should start having translations? -Allen, KDEPIM Release Dude [1] http://techbase.kde.org/Schedules/KDE4/4.0_Release_Roadmap#Milestone:_Beta_Cycle
Allen Winter wrote: > According to the milestones [1] we are currently in a message freeze. > Obviously that needs to be changed. According to http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule Message Freeze is scheduled on August 20, 2007. > When would be a good time to have the message freeze? > After the second beta (25 Aug)? After the first release candidate? When will it be ready? :) Of course the more time the better for translators but I don't want KDE4 to be released with incomplete or obsolete messages (e.g. DCOP communication error). > What release should start having translations? ASAP so translation bugs can be spotted by beta testers, and personally I've got something to test. :) Yukiko
While we are talking about this issue... How you are guys working? Using kbabel4? or kbabel3? or Kaider...? ביום ראשון, 5 באוגוסט 2007, נכתב על ידי Yukiko Bando: > Allen Winter wrote: > > According to the milestones [1] we are currently in a message freeze. > > Obviously that needs to be changed. > > According to http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule > Message Freeze is scheduled on August 20, 2007. > > > When would be a good time to have the message freeze? > > After the second beta (25 Aug)? After the first release candidate? > > When will it be ready? :) Of course the more time the better for > translators but I don't want KDE4 to be released with incomplete or > obsolete messages (e.g. DCOP communication error). > > > What release should start having translations? > > ASAP so translation bugs can be spotted by beta testers, and personally > I've got something to test. :) > > Yukiko
On 06/08/07, Rinse de Vries <rinsedevries <at> kde.nl> wrote: > Op zondag 05 augustus 2007, schreef Diego Iastrubni: > > How you are guys working? Using kbabel4? or kbabel3? or Kaider...? > > I use kbabel3, some of my team use kaider. > > AFAIK kbabel4 doesn't exist. KBabel has been damaged while porting it to KDE 4. It is not in a very usable state, but it exists in SVN. I use KBabel from KDE 3 and the po mode for vim depending on what I want to do. I used KAider once in a very early state, but wasn't able to compile KDE 4 stuff recently (due to computer issues, not KDE issues). regards
Am Donnerstag, 9. August 2007 01:35:02 schrieb Frederik Schwarzer: > On 06/08/07, Rinse de Vries <rinsedevries <at> kde.nl> wrote: > > Op zondag 05 augustus 2007, schreef Diego Iastrubni: > > > How you are guys working? Using kbabel4? or kbabel3? or Kaider...? > > > > I use kbabel3, some of my team use kaider. > > > > AFAIK kbabel4 doesn't exist. > > KBabel has been damaged while porting it to KDE 4. It is not in a very > usable state, but it exists in SVN. > I use KBabel from KDE 3 and the po mode for vim depending on what I want to > do. I used KAider once in a very early state, but wasn't able to compile > KDE 4 stuff recently (due to computer issues, not KDE issues). KAider is already in a at least usable state. Of course it's still missing a lot of features that we're used from KBabel. But on the other hand, KAider needs translators for real life testing. cheers thomas
Am Donnerstag 09 August 2007, 08:51:18 schrieb Thomas Reitelbach: > KAider is already in a at least usable state. > Of course it's still missing a lot of features that we're used from KBabel. > But on the other hand, KAider needs translators for real life testing. I did some translation work with kaider too. The basic functions work, but be careful with headers and settings before you check in your translations. There are (were?) some flaws. I monitor the svn changes of kaider and the last commits looked promising. If we all wait for a rock stable kaider we probably find bugs only short before the KDE 4 release. Stephan
Hiya, On Saturday 04 August 2007 09:22:32 am Allen Winter wrote: > Howdy, > > According to the milestones [1] we are currently in a message freeze. > Obviously that needs to be changed. > Hmm. The release schedule says that the strings freeze occurs on Aug 20th: http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule#August_20.2C_2007:_Message_Freeze regards, Jason
On Saturday 04 August 2007 12:35:15 pm Jason Harris wrote: > Hiya, > > On Saturday 04 August 2007 09:22:32 am Allen Winter wrote: > > Howdy, > > > > According to the milestones [1] we are currently in a message freeze. > > Obviously that needs to be changed. > > > Hmm. The release schedule says that the strings freeze occurs on Aug 20th: > http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule#August_20.2C_2007:_Message_Freeze > Yeah, I vaguely recall doing that. It was just a wild guess. But Chusslove thinks any message freeze before September is too early.
On Saturday 04 August 2007 18:22, Allen Winter wrote: > > When would be a good time to have the message freeze? If we go with the current planning of release and announcement, I guess it would make sense to plan the message freeze relative to the launch event at Mountainview (which probably will be mid or end of January). -- -- Cornelius Schumacher <schumacher@...>
Op za 4 aug 2007 21:51 schreef u: > On Saturday 04 August 2007 18:22, Allen Winter wrote: > > > > When would be a good time to have the message freeze? > > If we go with the current planning of release and announcement, I guess it > would make sense to plan the message freeze relative to the launch event at > Mountainview (which probably will be mid or end of January). > So, the plan is not to release oct 23rd ? I mean, if we want to make a release around that date, a message freeze in Januari is... weird. I guess I'm missing something here. Toma
On Saturday 04 August 2007 22:14, Tom Albers wrote: > Op za 4 aug 2007 21:51 schreef u: > > On Saturday 04 August 2007 18:22, Allen Winter wrote: > > > When would be a good time to have the message freeze? > > > > If we go with the current planning of release and announcement, I guess > > it would make sense to plan the message freeze relative to the launch > > event at Mountainview (which probably will be mid or end of January). > > So, the plan is not to release oct 23rd ? I mean, if we want to make a > release around that date, a message freeze in Januari is... weird. I guess > I'm missing something here. No, the plan is to release October 23rd, but the big official announcement and launch event is in January. So it might be good to plan to have a translated version of the desktop in January and not in October (thus planning _relative_ to January, not having the freeze in January). This would make it possible to move the message freeze to a later date (say November). It obviously would also mean that the 4.0.0 release (which happens in October) wouldn't be translated that well, but I guess that would be ok, given that the focus of 4.0.0 is the platform and not the desktop. The 4.0.x release which is current at the launch event of course should be translated as well as possible. -- -- Cornelius Schumacher <schumacher@...>
RSS Feed