Re: The road to 4.3
On Tuesday 31 March 2009 00:25:54 Albert Astals Cid wrote: > As said i'm and the i18n teams seem to be OK with that, so you can go to > the wiki and edit it yourself ;-) Okay. :D -Riccardo -- GPG key: 3D0F6376 When encrypting, please encrypt also for this subkey: 9EBD7FE1 - Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke 和平 Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini Peoch שלום Shanti Vrede Baris Rój Mír Taika Rongo Sulh Mir Py'guapy 평화 ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: The road to 4.3
A Dilluns, 30 de març de 2009, Riccardo Iaconelli va escriure: > On Sunday 25 January 2009 22:34:50 Albert Astals Cid wrote: > > A Diumenge, 25 de gener de 2009, Riccardo Iaconelli va escriure: > > > On Monday 05 January 2009 17:04:58 Albert Astals Cid wrote: > > > > Done, waiting for feedback. > > > > > > Any news? > > > > Not really, just one team answered saying it was ok if the number of new > > texts was small, so i think that if artists want we can add that explicit > > excemption. > > Found this mail back in the archives... I completely forgot about it... > sorry! :\ > > Can we please get this explicit exception? Texts shouldn't be big, I think > names of themes/wallpapers will be the only strings... but it will give us > some more flexibility and the possibility to add e.g. the default wallpaper > only in the RC cycles, so that we keep a fresh look for the new release. =) As said i'm and the i18n teams seem to be OK with that, so you can go to the wiki and edit it yourself ;-) Albert > > Bye, > -Riccardo ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: The road to 4.3
On Sunday 25 January 2009 22:34:50 Albert Astals Cid wrote: > A Diumenge, 25 de gener de 2009, Riccardo Iaconelli va escriure: > > On Monday 05 January 2009 17:04:58 Albert Astals Cid wrote: > > > Done, waiting for feedback. > > > > Any news? > > Not really, just one team answered saying it was ok if the number of new > texts was small, so i think that if artists want we can add that explicit > excemption. Found this mail back in the archives... I completely forgot about it... sorry! :\ Can we please get this explicit exception? Texts shouldn't be big, I think names of themes/wallpapers will be the only strings... but it will give us some more flexibility and the possibility to add e.g. the default wallpaper only in the RC cycles, so that we keep a fresh look for the new release. =) Bye, -Riccardo -- GPG key: 3D0F6376 When encrypting, please encrypt also for this subkey: 9EBD7FE1 - Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke 和平 Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini Peoch שלום Shanti Vrede Baris Rój Mír Taika Rongo Sulh Mir Py'guapy 평화 ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: The road to 4.3
A Diumenge, 25 de gener de 2009, Riccardo Iaconelli va escriure: > On Monday 05 January 2009 17:04:58 Albert Astals Cid wrote: > > Done, waiting for feedback. > > Any news? Not really, just one team answered saying it was ok if the number of new texts was small, so i think that if artists want we can add that explicit excemption. Albert > > -Riccardo ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: The road to 4.3
On Monday 05 January 2009 17:04:58 Albert Astals Cid wrote: > Done, waiting for feedback. Any news? -Riccardo -- GPG key: 3D0F6376 When encrypting, please encrypt also for this subkey: 9EBD7FE1 - Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke 和平 Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini Peoch שלום Shanti Vrede Baris Rój Mír Taika Rongo Sulh Mir Py'guapy 평화 ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: The road to 4.3
A Dilluns 05 Gener 2009, Tom Albers va escriure: > Op maandag 05 januari 2009 01:00 schreef u: > > A Dissabte 03 Gener 2009, Tom Albers va escriure: > > > Hi, > > > > > > I've put up a schedule for 4.3. > > > > > > As we have Akademy on 3rd of July, I've planned to have released RC1 by > > > that date, as we branch at that stage, trunk is open for features > > > during Akademy. > > > > > > I've cancelled the Alfa release, as it brings almost no feedback. We > > > can add it to the schedule later on when we see some massive code > > > changes in 4.3, which warrants an extra release. > > > > > > Let me know when the schedule is wrong for some reason. > > > > > > http://techbase.kde.org/Schedules/KDE4/4.3_Release_Schedule > > > > > > I'ld like to announce this schedule to k-c-d by the end of next week. > > > > An artist complained to me today that the Artwork freeze is after the > > Message freeze but most of the times new Artwork needs new Messages so > > either we add an explicit allowance for breaking the Message freeze or we > > add an explicit warning that the Artwork Freeze can't touch any Message. > > I think the l10n people should decide if the exception is ok. If not we > need to go for the explicit warning. > > Can you bring it up on the l10n ml? Done, waiting for feedback. Albert > > Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: The road to 4.3
Op maandag 05 januari 2009 01:00 schreef u: > A Dissabte 03 Gener 2009, Tom Albers va escriure: > > Hi, > > > > I've put up a schedule for 4.3. > > > > As we have Akademy on 3rd of July, I've planned to have released RC1 by > > that date, as we branch at that stage, trunk is open for features during > > Akademy. > > > > I've cancelled the Alfa release, as it brings almost no feedback. We can > > add it to the schedule later on when we see some massive code changes in > > 4.3, which warrants an extra release. > > > > Let me know when the schedule is wrong for some reason. > > > > http://techbase.kde.org/Schedules/KDE4/4.3_Release_Schedule > > > > I'ld like to announce this schedule to k-c-d by the end of next week. > > An artist complained to me today that the Artwork freeze is after the Message > freeze but most of the times new Artwork needs new Messages so either we add > an explicit allowance for breaking the Message freeze or we add an explicit > warning that the Artwork Freeze can't touch any Message. I think the l10n people should decide if the exception is ok. If not we need to go for the explicit warning. Can you bring it up on the l10n ml? Toma___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: The road to 4.3
A Dissabte 03 Gener 2009, Tom Albers va escriure: > Hi, > > I've put up a schedule for 4.3. > > As we have Akademy on 3rd of July, I've planned to have released RC1 by > that date, as we branch at that stage, trunk is open for features during > Akademy. > > I've cancelled the Alfa release, as it brings almost no feedback. We can > add it to the schedule later on when we see some massive code changes in > 4.3, which warrants an extra release. > > Let me know when the schedule is wrong for some reason. > > http://techbase.kde.org/Schedules/KDE4/4.3_Release_Schedule > > I'ld like to announce this schedule to k-c-d by the end of next week. An artist complained to me today that the Artwork freeze is after the Message freeze but most of the times new Artwork needs new Messages so either we add an explicit allowance for breaking the Message freeze or we add an explicit warning that the Artwork Freeze can't touch any Message. Albert > > Toma ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: The road to 4.3
On Saturday 03 January 2009 20:52:01 Tom Albers wrote: > Op Saturday 03 January 2009 20:14 schreef u: > > it would be great if we could do a beta (or whatever you want to call it) > > every two weeks to allow for a faster test-fix-test cycle during the > > stabilization (non-feature-dev) period of the cycle. > > Please note that there is a week between tagging and releaseing. I > considered reducing the time in my previous mails, but it requires a faster > tagging to release period. > > So without changing the week between tag and release it goes like this for > a 2 week cycle: week 1 wednesday: tagging b1 > week 2 wednesday: releasing b1 > week 3 wednesday: tagging b2 > week 4 wednesday: releasing b2 > > Which effectively means that you have 1 week to get the bugs and fix them, > though receiving bugs during week 3 is not that bad, new fixes can not > longer be added to b2. > > So, to work with a 2 weeks beta cycle, we need to reduce the period between > tag and release: Week 1 monday: tag b1 > Week 1 wednesday: release b1 > Week 3 wednesday: tag b2 > Week 3 friday: release b2 > > Which effectively means that the period has increased to 2 weeks, which is > a lot better imho. As a packager I won't mind a shorter period, but if tarballs is released late monday and release is early wednesday, it effectively only gives a full day of packaging work, which I think it is a bit too short. Especially when many kde packagers are volunteers who might not be able to take that tuesday off to do packaging. Giving two full days between "tarball packager release" and release will at least be better. Alternatively, skip the period between tagging and releasing and just let distros catch up as fast as they can. /Sune -- How might I install on the tower? You must get access over a forward in order to open a hard disk. signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: The road to 4.3
On Saturday 03 January 2009, Tom Albers wrote: > So, to work with a 2 weeks beta cycle, we need to reduce the period between > tag and release: Week 1 monday: tag b1 > Week 1 wednesday: release b1 > Week 3 wednesday: tag b2 > Week 3 friday: release b2 > > Which effectively means that the period has increased to 2 weeks, which is > a lot better imho. if this is possible and realistic to achieve without causing the release team to tear their hair out and run screaming, it would be wonderful. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: The road to 4.3
Op Saturday 03 January 2009 20:14 schreef u: > it would be great if we could do a beta (or whatever you want to call it) > every two weeks to allow for a faster test-fix-test cycle during the > stabilization (non-feature-dev) period of the cycle. Please note that there is a week between tagging and releaseing. I considered reducing the time in my previous mails, but it requires a faster tagging to release period. So without changing the week between tag and release it goes like this for a 2 week cycle: week 1 wednesday: tagging b1 week 2 wednesday: releasing b1 week 3 wednesday: tagging b2 week 4 wednesday: releasing b2 Which effectively means that you have 1 week to get the bugs and fix them, though receiving bugs during week 3 is not that bad, new fixes can not longer be added to b2. So, to work with a 2 weeks beta cycle, we need to reduce the period between tag and release: Week 1 monday: tag b1 Week 1 wednesday: release b1 Week 3 wednesday: tag b2 Week 3 friday: release b2 Which effectively means that the period has increased to 2 weeks, which is a lot better imho. Toma___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: The road to 4.3
On Saturday 03 January 2009, Tom Albers wrote: > Hi, > > I've put up a schedule for 4.3. > > As we have Akademy on 3rd of July, I've planned to have released RC1 by > that date, as we branch at that stage, trunk is open for features during > Akademy. sounds great. > I've cancelled the Alfa release, as it brings almost no feedback. We can > add it to the schedule later on when we see some massive code changes in > 4.3, which warrants an extra release. agreed > http://techbase.kde.org/Schedules/KDE4/4.3_Release_Schedule question for developers, perhaps: how did they find the 6 weeks of beta and bug fixing this time around? enough time, not enough time, too long? how about the number of betas made? it would be great if we could get some feedback from developers (e.g. a small online survey) regarding things like this. after 4 months of feature dev, spending 1.5 months not doing feature dev (counting from the start of beta1) was a bit of a long singular chunk, but had value. a month between betas, however, was really unfortunate for us in plasma. within the first week of beta2, we had the bulk of issues reported and subsequently fixed. week 2 saw some more fixes, but far fewer new issues (though no end to the reporting =), but by week three reports coming in were nearly all duplicates, and fixed dupes at that. it would be great if we could do a beta (or whatever you want to call it) every two weeks to allow for a faster test-fix-test cycle during the stabilization (non-feature-dev) period of the cycle. apparently a huge % of our reporting testers these days are using binaries and not building from source, so this really impacts the ability for people to test fixes, find regressions introduced by those fixes and report new issues that were obscured by the previous problems. of course, this could be unique to workspace type apps like plasma and other apps may see no real value in quicker test-fix-test cycles. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
The road to 4.3
Hi, I've put up a schedule for 4.3. As we have Akademy on 3rd of July, I've planned to have released RC1 by that date, as we branch at that stage, trunk is open for features during Akademy. I've cancelled the Alfa release, as it brings almost no feedback. We can add it to the schedule later on when we see some massive code changes in 4.3, which warrants an extra release. Let me know when the schedule is wrong for some reason. http://techbase.kde.org/Schedules/KDE4/4.3_Release_Schedule I'ld like to announce this schedule to k-c-d by the end of next week. Toma___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
