Release schedule timing presentation
The timing on the release schedule* is confusing. Eg 1.25 Tuesday, April 3, 2012: KDE SC 4.8.2 release - you'd think we were going to release yesterday. So I enabled publishing on our repo. But according to Dirk, to clarify developer uncertainty about how late on tagging day one can commit, the following phrase was inserted All deadlines are due 23:59 UTC, but if you need a few more hours, notify someone from the release team. which puts 4.8.2 being released at earliest at Wednesday April 4 01:59 CEST, if you count a release as a deadline. I'd like to separate the code freeze/tagging deadlines from the release schedule so that users, press and idiot distributors like myself can easily see when things should happen IIRC there is a script to generate the schedule, anyone know where it is? Will *http://techbase.kde.org/Schedules/KDE4/4.8_Release_Schedule ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Release schedule timing presentation
El Dimecres, 4 d'abril de 2012, a les 11:47:53, Will Stephenson va escriure: The timing on the release schedule* is confusing. Eg 1.25 Tuesday, April 3, 2012: KDE SC 4.8.2 release - you'd think we were going to release yesterday. So I enabled publishing on our repo. But according to Dirk, to clarify developer uncertainty about how late on tagging day one can commit, the following phrase was inserted All deadlines are due 23:59 UTC, but if you need a few more hours, notify someone from the release team. which puts 4.8.2 being released at earliest at Wednesday April 4 01:59 CEST, if you count a release as a deadline. I think your problem is easily solved by looking at the kde.org webpage and having a look to see if the announcement is out or not. I'd like to separate the code freeze/tagging deadlines from the release schedule so that users, press and idiot distributors like myself can easily see when things should happen IIRC there is a script to generate the schedule, anyone know where it is? playground/utils/releaseschedule Albert Will *http://techbase.kde.org/Schedules/KDE4/4.8_Release_Schedule ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Release schedule timing presentation
On Wednesday 04 Apr 2012 18:23:30 Albert Astals Cid wrote: which puts 4.8.2 being released at earliest at Wednesday April 4 01:59 CEST, if you count a release as a deadline. I think your problem is easily solved by looking at the kde.org webpage and having a look to see if the announcement is out or not. As a distributor, I like to have the packages out there shortly before the announcement is out (typically at about 4pm Europe time) otherwise they are not out and mirrored until the next day. Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Re: Stepping down as release coordinator for KDE 4.9+
On Fri, Mar 30, 2012 at 01:27:43PM +0200, Dirk Mueller wrote: Well, the day had to come. I realize that my focus is meanwhile on many other tasks, and I don't have enough time and attention to follow KDE 4.9.x development. Shame to see you go but thanks for stepping down gracefully. I would be interested in helping but I think it's a bit of a conflict of interest when distro people make tars for distros so I wouldn't be the best candidate. Honestly, I don't expect this to be a problem. Sure, you're involved with different hats, but that is the case for many of us, and it usually works very well. Being conscient about possible conflicts of interest is important, but in the end, it all boils down to getting work done. Usually, distro people are very suitable for specifically being on the fenceline 'where we throw tarballs over the wall', as distro packager, you'll have a pretty good feeling if some last minute bug is actually a showstopper, and warrants respinning tarballs or delaying a release for a day (which is, in my experience the vast majority of critical decisions). If you feel that your distro role doesn't allow you to speak neutrally for the release team, then scratch your head if it is an _actual_ problem, if it persists, ask someone else to jump in. I personally consider you a very integre guy, and maybe the fact that you seem to be more concerned about this than anybody around you already says enough. :) -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Stepping down as release coordinator for KDE 4.9+
Hey Dirk, others, Well, the day had to come. I realize that my focus is meanwhile on many other tasks, and I don't have enough time and attention to follow KDE 4.9.x development. I can finish the 4.8.x series, but I would like to hand the work for 4.9.x and beyond over to somebody else. Any volunteers appreciated. I can help with understanding the current scriptcollection and documenting things to get a new person up to speed. Volunteers appreciated! First of all, I would like to say a HUGE thanks to Dirk, who has been our central release dude for years. You've been one of the reliable cornerstones that have made a long series of releases possible and delivered. Chapeau and thanks for the excellent work done. Then, from a personal point of view, as we've been working together closely on more than hundred releases: It has been a great pleasure, and our cooperation was always excellent, thanks for being such a reliable release buddy! :) Moving on, I'm happy that some people already expressed that they're willing to help out. What would be important from my point is to have clear knowledge who takes care of the getting tarballs onto our mirrors. The actual work can I think best be distributed over a team where people can fall back onto each other. I think we should get together for an IRC meeting and come up with a cunning plan how we are going to tackle releasing our software starting with 4.9.0, and use the intermittent 4.8 stable updates and pre-releases to 4.9.0 as transition period. Maybe Jonathan and Allen would be willing to spearhead this, getting together people, and splitting up the work in a meaningful manner. I can help out getting this organised as well, and I think it would be good to invite one or more sysadmins to weigh on tooling, infrastructural, etc. questions. I'm personally still available to do the announcement and PR side, and happy to work with you all. :) Cheers -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
