As decided by FESCo on 2012-12-05 meeting, all proposed Features are required
to pass through the community review by announcing them on devel-announce list.
FESCo votes on new features no sooner than a week from the announcement.
= Features/Php55 =
https://fedoraproject.org/wiki/Features/Php55
* Detailed description:
To provide the latest PHP stack
Upstream roadmap (see TODO)
- PHP 5.5.0alpha1 is released (Nov 22th)
- PHP 5.5.0alpha2 is released (Dec 18th)
- PHP 5.5.0beta is planed for January (feature freeze)
Finale version (Q1/2013) should be available before fedora 19 (Q2/2013).
Planed packaging changes
Build more extensions shared for flexibility
- in php-common: bz2, calendar, ctype, exif, ftp, gettext, iconv, sockets
and tokenizer
- moved in php-gmp: gmp
- moved in php-process: shmop
- moved in php-xml: xml and simplexml
Dtrace enabled build
Jaroslav
As decided by FESCo on 2012-12-05 meeting, all proposed Features are required
to pass through the community review by announcing them on devel-announce list.
FESCo votes on new features no sooner than a week from the announcement.
= Features/PackageSignatureCheckingDuringInstall =
https://fedoraproject.org/wiki/Features/PackageSignatureCheckingDuringInsta…
* Detailed description:
One long-standing problem in Fedora is that we don't check package signatures
during installation. This has been a persistent issue since the very beginning
of Fedora (and even in Red Hat Linux before it.) The reason for this has
always been that there's no way to form any root of trust for the signatures
in the repositories, and thus no reason they wouldn't have been modified along
with whatever package would need to be re-signed after tampering.
Following the implementation of Features/SecureBoot, we can extend the Secure
Boot keys as a root of trust provided by the hardware against which we can
verify a signature on our key files, thus guaranteeing that they're from the
same source as the boot media.
Jaroslav
As decided by FESCo on 2012-12-05 meeting, all proposed Features are required
to pass through the community review by announcing them on devel-announce list.
FESCo votes on new features no sooner than a week from the announcement.
= Features/NodeJS =
https://fedoraproject.org/wiki/Features/NodeJS
* Detailed description:
Node.js is a platform built on Chrome's JavaScript runtime for easily building
fast, scalable network applications. Node.js uses an event-driven, non-blocking
I/O model that makes it lightweight and efficient, perfect for data-intensive
real-time applications that run across distributed devices.
Jaroslav
As decided by FESCo on 2012-12-05 meeting, all proposed Features are required
to pass through the community review by announcing them on devel-announce list.
FESCo votes on new features no sooner than a week from the announcement.
= Features/NetworkManagerCLIAddConnection =
https://fedoraproject.org/wiki/Features/NetworkManagerCLIAddConnection
* Detailed description:
Administrators will be able to configure new connections via a simple
command-line interface. It will be possible to create and activate new
connections, as well as delete them.
Jaroslav
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
Hi,
I plan to rebase poppler in rawhide to poppler-0.22.0 at the beginning
of next week.
There are several API changes and 1 soname bump (libpoppler.so.26 to
libpoppler.so.34).
The API changes are mostly new functions but also some removals and
moves of members between public and private sections.
You can test your package against this scratch build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=4845665
Regards
Marek
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
As decided by FESCo on 2012-12-05 meeting, all proposed Features are required
to pass through the community review by announcing them on devel-announce list.
FESCo votes on new features no sooner than a week from the announcement.
= Features/3D Printing =
https://fedoraproject.org/wiki/Features/3D_Printing
* Detailed description:
There are several software needs for a 3D printer users: 3D modeling tool,
such as OpenSCAD or Blender; slcing tool, to "compile" the 3D model to a set of
G-Code instructions, such as Skeinforge or Slic3r; and finally a printer control
software, such as Printrun, Cura or RepetierHost.
Other useful application is meshlab, that allows users to view STL files, but it
is already in Fedora, so it is not mentioned more.
3D Printing Feature is already being discussed on fedora-devel list,
http://lists.fedoraproject.org/pipermail/devel/2012-December/175711.html
Jaroslav
As decided by FESCo on 2012-12-05 meeting, all proposed Features are required
to pass through the community review by announcing them on devel-announce list.
FESCo votes on new features no sooner than a week from the announcement.
= Features/Pillow =
https://fedoraproject.org/wiki/Features/Pillow
* Detailed description:
The PIL project has been rather inactive lately (last release in 2009), and one
big issue is the missing python 3 compatibility. There seems to be some general
agreement that Pillow [1] is a likely candidate to succeed PIL, and in particular
to bring python 3 support, see the discussion at [2]. Pillow describes itself as
"Pillow is the "friendly" PIL fork. PIL is the Python Imaging Library. Pillow was
started for and is currently maintained by the Plone community. But it is used by
many other folks in the Python web community, and probably elsewhere too."
The fork author's goal is to foster packaging improvements via:
- Publicized development and solicitation of community support.
- Exploration of packaging problems within the fork, most noticably
via adding setuptools support but also via clean up & refactoring
of packaging code.
Pillow is practically a drop-in replacement for PIL, except one small issue (see below).
For Python 3, there is a fork which offers Py3 compatibility here [3]. The patches are
planed for review and merge into Pillow, see [4].
[1] https://github.com/python-imaging/Pillow/
[2] http://mail.python.org/pipermail/image-sig/2012-October/007059.html
[3] https://github.com/fluggo/Pillow
[4] http://mail.python.org/pipermail/image-sig/2012-December/007120.html
Pillow Feature is already being discussed on fedora-devel list,
http://lists.fedoraproject.org/pipermail/devel/2012-December/175621.html
---
Btw. If you have any concerns about the announcements (format, frequency, ml etc.),
please let me know.
Jaroslav
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