Announcements to packagers policy - question
Hi all, I was made aware today that, unlike beta releases, RC releases seem not to be announced on the packagers list. Is there a reason for that? Thanks for the answer in advance :) Regards, Myriam -- Proud member of the Amarok and KDE Community Protect your freedom and join the Fellowship of FSFE: http://www.fsfe.org Please don't send me proprietary file formats, use ISO standard ODF instead (ISO/IEC 26300) ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Announcements to packagers policy - question
--- El mar, 17/7/12, Myriam Schweingruber escribió: Hi all, I was made aware today that, unlike beta releases, RC releases seem not to be announced on the packagers list. Is there a reason for that? What's the need of the announcement to be posted there? It's not like there is not enough places we annouce the release has been made, like this list, the annoucements mailing list, the webpage, etc. Did any packager really miss we released RC1 or RC2? Cheers, Albert Thanks for the answer in advance :) Regards, Myriam -- Proud member of the Amarok and KDE Community Protect your freedom and join the Fellowship of FSFE: http://www.fsfe.org Please don't send me proprietary file formats, use ISO standard ODF instead (ISO/IEC 26300) ___ 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: Announcements to packagers policy - question
On Tuesday, July 17, 2012 11:14:12 AM Albert Astals Cid wrote: --- El mar, 17/7/12, Myriam Schweingruber escribió: Hi all, I was made aware today that, unlike beta releases, RC releases seem not to be announced on the packagers list. Is there a reason for that? What's the need of the announcement to be posted there? It's not like there is not enough places we annouce the release has been made, like this list, the annoucements mailing list, the webpage, etc. Did any packager really miss we released RC1 or RC2? I did. Others on the Kubuntu team knew about it, but I've relied on those announcements on the packager's list (particularly about when the pre-release tarballs are available - AFAIK that isn't announced anywhere else). If you're going to drop communication methods that people rely on, it would be nice to mention it in advance. What low volume mailing list should I subscribe to so I can find out about pre-release tarballs and release announcements? Scott K ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Virtuoso 6.1.5 is buggy
Hey everyone Please avoid using Virtuoso 6.1.5 with Nepomuk from kde 4.9. The Nepomuk team won't support any installation using virtuoso 6.1.5, there is a known regression that will make most user visible features fail (like searching), so please do not ship with it. Virtuoso 6.1.4 is fine. And the virtuoso team have notified us that they'll be release 6.1.6 in a couple of days. We are in the process of testing it out. Thanks -- Vishesh Handa ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Virtuoso 6.1.5 is buggy
Tirsdag den 17. juli 2012 20:38:25 Vishesh Handa skrev: Please avoid using Virtuoso 6.1.5 with Nepomuk from kde 4.9. Does that imply virtuoso 6.1.5 + KDE SC 4.8.x is a safe combo? ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Virtuoso 6.1.5 is buggy
On 07/17/2012 10:25 AM, Martin Schlander wrote: Tirsdag den 17. juli 2012 20:38:25 Vishesh Handa skrev: Please avoid using Virtuoso 6.1.5 with Nepomuk from kde 4.9. Does that imply virtuoso 6.1.5 + KDE SC 4.8.x is a safe combo? reportedly yes (or at least better off than 6.1.5 + 4.9 anyway) -- rex ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Virtuoso 6.1.5 is buggy
Please keep me cced. Tirsdag den 17. juli 2012 20:38:25 Vishesh Handa skrev: Please avoid using Virtuoso 6.1.5 with Nepomuk from kde 4.9. Does that imply virtuoso 6.1.5 + KDE SC 4.8.x is a safe combo? Yup that's fine. On Tue, Jul 17, 2012 at 8:38 PM, Vishesh Handa m...@vhanda.in wrote: Hey everyone Please avoid using Virtuoso 6.1.5 with Nepomuk from kde 4.9. The Nepomuk team won't support any installation using virtuoso 6.1.5, there is a known regression that will make most user visible features fail (like searching), so please do not ship with it. Virtuoso 6.1.4 is fine. And the virtuoso team have notified us that they'll be release 6.1.6 in a couple of days. We are in the process of testing it out. Thanks -- Vishesh Handa -- Vishesh Handa ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Review Request: only remove old parent nodes' pointer when add new parent
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/105601/ --- Review request for Release Team and Andreas Cord-Landwehr. Description --- Do not remove child pointers in rooted tree if addeding the parent. It's part of 303570 bug's fix This addresses bug 303570. http://bugs.kde.org/show_bug.cgi?id=303570 Diffs - src/Plugins/DataStructure/RootedTree/RootedTreeNode.cpp ddbf6cb Diff: http://git.reviewboard.kde.org/r/105601/diff/ Testing --- Thanks, Wagner de Melo Reck ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Announcements to packagers policy - question
El Dimarts, 17 de juliol de 2012, a les 09:32:50, Scott Kitterman va escriure: On Tuesday, July 17, 2012 11:14:12 AM Albert Astals Cid wrote: --- El mar, 17/7/12, Myriam Schweingruber escribió: Hi all, I was made aware today that, unlike beta releases, RC releases seem not to be announced on the packagers list. Is there a reason for that? What's the need of the announcement to be posted there? It's not like there is not enough places we annouce the release has been made, like this list, the annoucements mailing list, the webpage, etc. Did any packager really miss we released RC1 or RC2? I did. Others on the Kubuntu team knew about it, but I've relied on those announcements on the packager's list (particularly about when the pre-release tarballs are available - AFAIK that isn't announced anywhere else). RC1 and RC2 did not have pre-release tarballs available, that is because the schedule says there's only one day between tagging and release, so it does not make any sense to do any kind of tarball pre-release. If you're going to drop communication methods that people rely on, it would be nice to mention it in advance. I already made clear on the packagers list that all public discussion about releases should happen here some weeks ago. What low volume mailing list should I subscribe to so I can find out about pre-release tarballs kde-packager and release announcements? kde-announce Cheers, Albert Scott K ___ 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: Review Request: only remove old parent nodes' pointer when add new parent
On July 17, 2012, 4:50 p.m., Albert Astals Cid wrote: We are not in a freeze at the moment, so the release team opinion is irrelevant. Cheers, Albert Aren't we at RC 2? This patch is also to be applied in the branch 4.9. greetings, Wagner - Wagner de Melo --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/105601/#review16014 --- On July 17, 2012, 4:23 p.m., Wagner de Melo Reck wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/105601/ --- (Updated July 17, 2012, 4:23 p.m.) Review request for Release Team and Andreas Cord-Landwehr. Description --- Do not remove child pointers in rooted tree if addeding the parent. It's part of 303570 bug's fix This addresses bug 303570. http://bugs.kde.org/show_bug.cgi?id=303570 Diffs - src/Plugins/DataStructure/RootedTree/RootedTreeNode.cpp ddbf6cb Diff: http://git.reviewboard.kde.org/r/105601/diff/ Testing --- Thanks, Wagner de Melo Reck ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
