Re: Release dates/nomenclature
On Saturday 01 September 2007 23:29, Allen Winter wrote: On Saturday 01 September 2007 11:45:07 am Thomas Zander wrote: On Saturday 01 September 2007 17:30:34 Matt Rogers wrote: That's no different than what we have now. The problem is that people seem to be too interested in fixing Krazy issues rather than fixing actual bugs. How do you propose we get them interested in fixing real bugs? Stop running the not-so-interresting krazy tests? ;) We can pull the plug on the EBN entirely. That's like turning off compiler warnings because you don't want people to fix them either. It's possible, but I'd rather try to rely on the discipline of our developers to fix what is needed. The EBN has always been a reporter of the last mile of little fixes; I don't think we've ever suggested that issues reported by the EBN are related to functionality, real bugs (defects encountered at runtime) or releaseability. The use of the words pull the plug garners a fuck it all, i'll reuse the domain for a LOLcats parody response from me. I don't think that will help get bugs fixed, but at least it will reduce the number unneeded re-compiles. I had no idea Krazy/EBN was doing such so harm to the project. That was not the intention. Communicate that to your developers. Give them priorities. Impress upon them the importance not of polishing th internals of the code until they shine, but on fixing the big ugly warts on the outside. There's a Sirius Cybernetics Corporation segue here, and I'm going to skip it. [ade] ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Release dates/nomenclature -- Revised proposal
I've seen no reaction to this email, but I think the current schedule (release 20 dec) is broken (Dirk is on vacation, it's too close to christmas for PR). Can I at least get a shut up, you're irrelevant answer, maybe something more promising? On Saturday 01 September 2007 15:57:57 Sebastian Kügler wrote: On Saturday 01 September 2007 12:28:31 Kevin Ottens wrote: So let's aim for a release on my mother's birthday, 13th December. I vote for 6th December, it's my father birthday. That would be the tagging date then :-) How about this, then. It's mainly what Dirk and Allen proposed. Thursday, 6 September: Release Beta2 (already tagged) September 24, 2007: Tagging Beta3 (This is a Monday, does that make sense?) October 2 2007: Release Beta3 October 22, 2007: Tagging Beta4 (Again, a Monday) October 30 2007: Release Beta4 (Beta4 is only 2 weeks long) November 5, 2007: Total Release Freeze (a Monday) November 13 2007: Tagging Release Candidate 1 (move closer to the freeze?) November 20 2007: Release Release Candidate 1 November 21 2007: Tagging Release Candidate 2 (to close to -rc1?) November 27 2007: Release Release Candidate 2 December 6 2007: Tagging final Release December 13 2007: Targeted Release Date * We should probably move the tagging and release for the following betas closer to each other, maybe tagging on Fridays, releasing on Tuesdays? Is that doable for testing and packaging? * Should we move tagging away from Monday? Or when will we suspend the BIC Monday? -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 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: Release dates/nomenclature -- Revised proposal
On Tuesday 04 September 2007 00:51, Allen Winter wrote: Also, I like Dirk's idea of a libs release in late October. I like this idea as well. The libs release should include kdesupport, kdelibs, and kdepimlibs Shouldn't it also include kdebase/runtime, so that it provides everything what is needed for third-party apps development? -- Cornelius Schumacher [EMAIL PROTECTED] ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
