logistics January 2013

logistics@lists.fedoraproject.org

4 participants
7 discussions

Call for tester/feedback on fedocal
by Pierre-Yves Chibon 12 Jan '13

12 Jan '13

Dear all, As announced before, over the last months, I have spent sometime working on a web-application that would allow us to manage calendar: fedocal. I started with the idea to replace the #fedora-meeting wiki page [1] which in addition from not being up to date relies on a mediawiki table which a number of person find really hard to handle/edit. Additionally it should be able to handle meeting reminder in a consistent and automated manner. I also had in mind to be able to have a calendar for the infrastructure, things like planned outage and all. I spoke with some person about this at the last FUDCon in Paris and they told me, it might be interesting to have a calendar also available for the ambassadors. Something that could/would replace the Events page [2]. This means that on the contrary to the #fedora-meeting calendar, the ambassador one can have several meetings at the same time and that we should be able to assign them to a region (EMEA/APAC/LATAM/NA). I took this into account and added the desired functionality to fedocal. I think I am now close to an alpha release so I would like to call for tester and feedback. Do you like it? Do you find it useful? What should be added? What simply doesn't work? All can go to fedocal's trac: http://fedorahosted.org/fedocal If you are interested, I also wrote down some documentation: http://fedocal.rtfd.org And of course, fedocal itself: https://fedocal.dev.fedoraproject.org It is still a very young project and I am still trying to determine if we want this and if it fits our needs. Thanks for your time. Best regards, Pierre [1] https://fedoraproject.org/wiki/Meeting_channel [2] https://fedoraproject.org/wiki/Events

2 1

The final Fedora 18 is RC4!
by Jaroslav Reznik 10 Jan '13

10 Jan '13

Hi, at today's supplementary Go/No-Go meeting it was decided to ship RC4 (release candidate) as the final release [1]. #agreed to ship RC4 as final release (with no votes against) The release date is Tuesday, January 15, 2013! Big thanks goes to everyone who helped with this RC3/RC4 testing effort and again to everyone who participated on the whole release. Time for Fedora 18 release parties! Jaroslav [1] http://meetbot.fedoraproject.org/fedora-meeting-2/2013-01-10/f18-go-no-go-s…

1 0

Fedora 18 status is Go, release planned for January 15, 2013
by Jaroslav Reznik 09 Jan '13

09 Jan '13

At the Fedora 18 Go/No-Go Meeting that just occurred, it was agreed to Go for the Fedora 18. The release is planned for Tuesday, January 15, 2013 [1]. See meeting minutes [2]. It was agreed that RC3 is GOLD for now, with possibility to raise the status of RC4 to be the final release based on outcome of supplemental testing due to the late acceptance of bug #810040 [3]. The final call will happen tomorrow, Thursday, January 10 at 16:00 UTC (11 AM EST, 8 AM PST, 17:00 CET), #fedora-meeting-2. Please help Fedora QA with supplemental testing - the RC2/RC3 test results will be pulled into the RC4 test matrices except the test cases required for RC4 re-verification. An email with more details will follow on Test list. Our lovely Spherical Cow would like to thank you everyone for that hard and sometimes dirty work that lead to it's release. Moooooooo! Jaroslav [1] http://fedoraproject.org/wiki/Releases/18/Schedule [2] http://meetbot.fedoraproject.org/fedora-meeting-2/2013-01-09/f18_final_gono… [3] https://bugzilla.redhat.com/show_bug.cgi?id=810040

1 0

Fedora 18 Go/No-Go Meeting, Wednesday, January 09 @ 19:00 UTC (2pm Eastern, 11am Pacific)
by Jaroslav Reznik 08 Jan '13

08 Jan '13

Join us on irc.freenode.net in #fedora-meeting-2 for this important meeting, wherein we shall determine the readiness of the Fedora 18. Wednesday, January 09, 2013 @19:00 UTC (14:00 EST/11:00 PST/20:00 CET) Due to conflicts in Meeting IRC channel and to give us the flexibility to have as long Go/No-Go as possible - we have to use #fedora-meeting-2 channel this time! "Before each public release Development, QA and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the Go/No-Go Meeting." "Verifying that the Release criteria are met is the responsibility of the QA Team." For more details about this meeting see: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime, keep an eye on the Fedora 18 Final Blocker list: http://qa.fedoraproject.org/blockerbugs/milestone/18/final/buglist Jaroslav

1 0

Fedora 18 Release Readiness Meeting :: Thursday, Jan. 03, 19:00 UTC (2pm Eastern, 11am Pacific)
by Jaroslav Reznik 04 Jan '13

04 Jan '13

Hi! After the holiday's break, let's continue with the effort to release our beloved Spherical Cow! Fedora 18 Release Readiness Meeting. date: 2013-01-03 place: irc.freenode.net in #fedora-meeting-1 time: 19:00 UTC (2 PM Eastern, 11 AM Pacific, 20:00 CET) This Thursday, January 03, we will meet to make sure we are coordinated and ready for the public release of Fedora 18 on Tuesday, January 08, 2013. Please note that this meeting will occur on January 03 *even if the release is delayed at the Go/No-Go meeting on the same day two hours earlier.* This meeting works best when we have representatives from all of the teams, so we'll be looking for the following people to attend or send a representative in their place. We will meet in #fedora-meeting-1 because of conflict in IRC meeting channel schedules. Ambassadors -- Jiri Eischmann Design -- Máirín Duffy Documentation -- Ben Cotton FESCo -- Kevin Fenzi Fedora Engineering Manager -- Tom "Spot" Callaway Fedora Project Leader -- Robyn Bergeron Infrastructure -- Kevin Fenzi Marketing -- Ruth Suehle Quality -- Adam Williamson Release Engineering -- Dennis Gilmore Translation -- Noriko Mizumoto Websites -- Kévin Raymond Thanks Jaroslav

2 2

Fedora 18 Final to slip by one week
by Jaroslav Reznik 03 Jan '13

03 Jan '13

Today at Go/No-Go meeting it was decided to slip Fedora 18 release by one week due to unresolved blocker bugs [1]. See the meeting minutes [2] for more details. As a result, Fedora 18 will be pushed out by one week with final release on 2013-01-15. Check current schedule [3]. The next Go/No-Go meeting is on Wednesday, Jan 09. Time will be announced on Monday. Please, help us with resolving currently accepted blocker bugs and review proposed bugs reported to your components. Thanks Jaroslav [1] http://qa.fedoraproject.org/blockerbugs/milestone/18/final/buglist [2] http://bit.ly/VzpMXH [3] http://fedoraproject.org/wiki/Releases/18/Schedule ============================================= #fedora-meeting-1: F18 Final Go/No-Go meeting ============================================= Meeting started by jreznik at 17:01:20 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2013-01-03/f18_final_gono… . Meeting summary --------------- * Roll Call (jreznik, 17:01:48) * Purpose of this meeting (jreznik, 17:07:00) * Purpose of this meeting is to see whether or not F18 Final is ready for shipment, according to the release criteria. (jreznik, 17:07:16) * This is determined in a few ways: (jreznik, 17:07:23) * No remaining blocker bugs (jreznik, 17:07:30) * Test matrices for Final are fully completed (jreznik, 17:07:37) * LINK: http://qa.fedoraproject.org/blockerbugs/milestone/18/final/buglist (jreznik, 17:07:44) * LINK: http://fedoraproject.org/wiki/Fedora_18_Final_Release_Criteria (jreznik, 17:07:49) * LINK: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test (jreznik, 17:07:55) * LINK: http://fedoraproject.org/wiki/Test_Results:Current_Installation_Test (jreznik, 17:08:00) * LINK: http://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test (jreznik, 17:08:05) * agenda (jreznik, 17:08:59) * current status (jreznik, 17:12:40) * Fedora 18 Final Test Compose (TC4) is available, no release candidate (RC) yet (jreznik, 17:13:44) * currently 7 blocker bugs are unresolved (not in ON_QA/VERIFIED/CLOSED state) based on accepted blocker bug list (jreznik, 17:14:56) * 3 proposed blockers (minus the KDE tracking one) (jreznik, 17:15:37) * "mini" review of accepted/proposed blocker bugs (jreznik, 17:17:56) * (891443) crash when reusing existing Btrfs volume (adamw, 17:20:20) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=891443 (adamw, 17:20:20) * Proposed Blocker, anaconda, NEW (adamw, 17:20:20) * AGREED: 891443 is accepted as a blocker per criterion "The installer's custom partitioning mode must be capable of the following: Creating, destroying and assigning mount points to partitions of any specified size using most commonly-used filesystem types" (adamw, 17:30:01) * (881624) U.S. keyboard layout used for encryption passphrase entry during fedup second phase (adamw, 17:30:12) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=881624 (adamw, 17:30:12) * Proposed Blocker, fedup, NEW (adamw, 17:30:12) * AGREED: taking into consideration the general tenor of the wider devel@ discussion, the fact that this is likely documentable and workaroundable and that it could well be fixed with an update to f17's fedup, 881624 is rejected as a blocker (adamw, 17:48:16) * (889699) systemd drops X11 keyboard layout settings during upgrade (adamw, 17:49:01) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=889699 (adamw, 17:49:01) * Proposed Blocker, systemd, ASSIGNED (adamw, 17:49:01) * AGREED: 889699 is accepted as a blocker per criterion "...it must be possible to successfully complete an upgrade from a fully updated installation of the previous stable Fedora release with that package set installed, using any officially recommended upgrade mechanisms. The upgraded system must meet all release criteria." in the case of non-U.S. keymaps (adamw, 18:20:21) * (888089) ValueError: A RAID0 set requires at least 2 members (adamw, 18:24:28) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=888089 (adamw, 18:24:28) * Accepted Blocker, anaconda, POST (adamw, 18:24:28) * this is now committed and awaiting a new anaconda build / compose / test cycle (adamw, 18:26:51) * (832510) vnc server starts before the network (adamw, 18:26:56) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832510 (adamw, 18:26:56) * Accepted Blocker, anaconda, NEW (adamw, 18:26:57) * developer (rvykydal) is on PTO this week, bcl is trying to take a look on the issue (jreznik, 18:29:22) * (877658) [i18n] some storage-related error messages not marked for translation: "Not enough free space on disks for automatic partitioning" (adamw, 18:29:38) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=877658 (adamw, 18:29:38) * Accepted Blocker, anaconda, ASSIGNED (adamw, 18:29:38) * this just needs an anaconda rebuild, should be fixed with a new build (adamw, 18:32:16) * (890577) drop to dracut shell if /usr is on a btrfs subvol (adamw, 18:32:26) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=890577 (adamw, 18:32:26) * Accepted Blocker, dracut, ON_QA (adamw, 18:32:27) * we need to do a TC5/RC1 with the updated dracut to fix and test this (adamw, 18:39:06) * (883075) fedup upgrading is too quiet (adamw, 18:39:37) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=883075 (adamw, 18:39:37) * Accepted Blocker, fedup-dracut, MODIFIED (adamw, 18:39:37) * this either needs some kind of action to build a new upgrade.img or can be considered done with tc4, need to clarify with tflink (adamw, 18:41:47) * (875846) [i18n] "ON" and "OFF" not translated in switches on DVD (gtk30.mo not on DVD) (adamw, 18:41:57) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=875846 (adamw, 18:41:57) * Accepted Blocker, lorax, ASSIGNED (adamw, 18:41:57) * this just needs a re-spin with new lorax (adamw, 18:43:21) * (889562) Console keymap set to "us" if you install with a keymap not provided by systemd-localed (adamw, 18:43:27) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=889562 (adamw, 18:43:27) * Accepted Blocker, systemd, NEW (adamw, 18:43:28) * plan here is to try and fix up the most prominent missing conversions in systemd's kbd-model-map where corresponding console keymaps are actually available (adamw, 18:49:31) * (876218) pxeboot/netinst + nfsiso repo = hang on reboot (adamw, 18:51:36) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=876218 (adamw, 18:51:36) * Accepted Blocker, systemd, ASSIGNED (adamw, 18:51:36) * we still seem to be playing hot potato between anaconda, systemd and nfs developers here. poettering believes it is an anaconda bug (adamw, 18:56:47) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=876218#c17 is relevant here. we *did* waive a similar bug for f17 final. qa in general thought that was a fudge too far. (adamw, 19:05:04) * ball is in development team's court, we need anaconda, systemd and nfs folks to agree on a plan and just fix the damn thing, jreznik and rbergeron please supervise (adamw, 19:15:18) * (891489) anaconda cannot find matching keyboard layouts for several languages, sets them to U.S. English (adamw, 19:15:48) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=891489 (adamw, 19:15:48) * Proposed NTH, anaconda, POST (adamw, 19:15:48) * AGREED: 891489 is accepted as NTH: it's a safe improvement to language->keymap mapping in anaconda which is desirable for non-english installs (adamw, 19:18:56) * (891487) Anaconda keyboard layout list is missing many offered by GNOME, including some associated with languages for which we offer a translation (adamw, 19:19:03) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=891487 (adamw, 19:19:03) * Proposed NTH, anaconda, NEW (adamw, 19:19:03) * AGREED: 891487 is accepted as NTH as a potential improvement in keymap availability, we may choose not to take the change if it is too big (adamw, 19:22:03) * (855250) Change the default filtering for Quick and Cangjie (adamw, 19:23:00) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=855250 (adamw, 19:23:00) * Proposed NTH, ibus-table-chinese, ASSIGNED (adamw, 19:23:00) * AGREED: 855250 accepted as NTH, improves default input config for Hong Kong users, safe change that does not affect anything else (adamw, 19:24:17) * (854557) Keyboard layout testing doesn't work as expected and lacks indication of the active layout (adamw, 19:24:27) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=854557 (adamw, 19:24:27) * Proposed NTH, anaconda, MODIFIED (adamw, 19:24:27) * AGREED: 854557 is rejected as NTH as the fix just clarifies the input dialog a bit, it doesn't improve the interface, and would necessitate new translations (adamw, 19:28:17) * go/no-go (jreznik, 19:28:57) * there's no RC build, there are outstanding accepted blockers, and test coverage is incomplete. so in accordance with policies, QA votes no-go (jreznik, 19:30:05) * AGREED: to no-go (jreznik, 19:31:19) * AGREED: to slip one week with release date on Tue 2012-01-15 and Go/No-Go meeting on Wed 2012-01-09 (jreznik, 20:04:42) * the possibility of another Fri Go/No-Go will be discussed in case of problems, with possibility to release on Thu 2012-01-17 (jreznik, 20:05:29) Meeting ended at 20:09:19 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * adamw (264) * jreznik (182) * nirik (102) * rbergeron (73) * poettering (61) * drago01_ (26) * drago01 (17) * dgilmore (17) * zodbot (7) * Martix (4) * kmacleod (4) * k0Do (4) * bcl (3) * rtcm (3) * dingtav (3) * jwb (3) * satellit (2) * j_dulaney (1) * BobLfoot (1) * tuanta (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Fedora 18 Go/No-Go Meeting, Thursday, January 03 @ 17:00 UTC (12pm Eastern, 9am Pacific)
by Jaroslav Reznik 02 Jan '13

02 Jan '13

Join us on irc.freenode.net in #fedora-meeting-1 for this important meeting, wherein we shall determine the readiness of the Fedora 18. Thursday, January 03, 2013 @17:00 UTC (12:00 EST/09:00 PST/18:00 CET) "Before each public release Development, QA and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the Go/No-Go Meeting." "Verifying that the Release criteria are met is the responsibility of the QA Team." For more details about this meeting see: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime, keep an eye on the Fedora 18 Final Blocker list: http://qa.fedoraproject.org/blockerbugs/milestone/18/final/buglist Reminder: Fedora 18 Final readiness meeting follows the Go/No-Go meeting two hours later (19:00 UTC, 2pm Eastern, 11am Pacific), even it's agreed on No-Go. There's also Fedora 18 Final Blocker Bug Review #8 meeting planned for January 02, 2013 17:00 UTC - if you have an accepted unresolved blocker bug, or proposed blocker bug assigned to you, please join the meeting to help us determine it's status. Jaroslav

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

logistics January 2013