devel-announce January 2013

devel-announce@lists.fedoraproject.org

9 participants
100 discussions

Proposed F19 Feature: GNOME 3.8
by Jaroslav Reznik 27 Jan '13

27 Jan '13

= Features/Gnome3.8 = https://fedoraproject.org/wiki/Features/Gnome3.8 Feature owner(s): Matthias Clasen <mclasen(a)redhat.com> Update GNOME to the latest upstream release. == Detailed description == GNOME 3.8 continues development along the lines of 3.6: * Building out the central features of GNOME 3: - A new panel will allow to configure GNOME shell search, and applications can provide search results to the shell - The display of search results in the GNOME shell overview was redesigned - Notifications can be configured in a new panel - Privacy settings are collected in a new panel - Sharing (mainly of data, in the local network) can be centrally controlled in a new panel * Support for OwnCloud in Online Accounts * Better accessibility * Improved IBus integration - Modifier-only shortcuts can be set in the Keyboard panel - IMEs can have menu items in the statusmenu (the whitelist was removed) - Per-window changes of input source are possible again - Nicer candidate popups * New applications - A note-taking app - A new photo app - A new clock app * Fallback mode is going away in 3.8. Instead, there will be a set of supported extensions that is grouped together in a 'classic' mode, which provides a more GNOME 2-like user experience

1 0

Proposed F19 Feature: GLIBC 2.17
by Jaroslav Reznik 27 Jan '13

27 Jan '13

= Features/GLIBC217 = https://fedoraproject.org/wiki/Features/GLIBC217 Feature owner(s): Jeff Law <law(a)redhat.com> Switch GLIBC in Fedora 19 to GLIBC version 2.17. == Detailed description == GLIBC 2.17 was released at the end of 2012; we have been closely tracking the GLIBC 2.17 development code in Fedora Rawhide and addressing any issues as they arise. The proposed mass-rebuild with GCC 4.8 [1] in February should also shake out any remaining problems with GLIBC's header files. [1] https://fedoraproject.org/wiki/Features/GCC48

1 0

Proposed F19 Feature: Cinnamon as Default Desktop
by Jaroslav Reznik 27 Jan '13

27 Jan '13

= Features/Cinnamon as Default Desktop = https://fedoraproject.org/wiki/Features/Cinnamon_as_Default_Desktop Feature owner(s): Eric Smith <eric(a)brouhaha.com> This feature proposes that Fedora switch the default desktop interface from Gnome 3 to Cinnamon. Cinnamon provides a desktop interface that is more familiar to Windows and Gnome 2 users than the standard Gnome Shell interface, while being built from Gnome 3 components. == Detailed description == The Gnome 3 interface is substantially different that the traditional desktop interfaces on both Linux and Windows. While it is good that there is research into new user interface concepts, many users prefer to have a traditional interface that they are accustomed to. Unfortunately it is difficult or impossible to assess what fraction of the user base prefers Gnome Shell vs. a more traditional interface. I'm not trying to start (or continue) a flame war here, so I won't state any of my own criticisms of Gnome Shell here, but I will observe that a number of very high profile people in the Linux community, such as Linus Torvalds and Alan Cox, have publicly announce that due to problems with Gnome Shell they are switching to a different desktop and/or Linux distribution. I submit the proposition that it is easier for a user doing a new Fedora install to start with a traditional desktop, and switch to the Gnome Shell if they prefer that, than to start with Gnome Shell and switch to a traditional desktop. The Cinnamon desktop provides a traditional desktop while being based on the latest Gnome and GTK components, so it seems like a better candidate for a default desktop than MATE, which is based on older components.

1 0

Proposed F19 Feature: systemd features
by Jaroslav Reznik 27 Jan '13

27 Jan '13

Announcing various systemd features in one announcement, see bellow: = Features/SystemdCalendarTimers = https://fedoraproject.org/wiki/Features/SystemdCalendarTimers Feature owner(s): Lennart Poettering <lennart at poettering dot net> systemd has supported timer units for activating services based on time since its inception. However, it only could schedule services based on monotonic time events (i.e. "every 5 minutes"). With this feature in place systemd also supports calendar time events (i.e. "every monday morning 6:00 am", or "at midnight on every 1st, 2nd, 3rd of each month if that's saturday or sunday"). = Features/SystemdHardwareDatabase = https://fedoraproject.org/wiki/Features/SystemdHardwareDatabase Feature owner(s): Kay Sievers <kay at redhat dot com> The udevd service has a long history of managing kernel devices. Besides generating events when devices are discovered or removed it maintains a dynamic, stateless database of all available devices including meta data about them. With Fedora 19 we want to substantially enhance the metadata that udev keeps for each device, by augmenting it from a userspace database of non- essential information, that is indexed by device identification data such as PCI/USB vendor/product IDs. = Features/SystemdLightweightContainers = https://fedoraproject.org/wiki/Features/SystemdLightweightContainers Feature owner(s): Lennart Poettering <lennart at poettering dot net> For a longer time systemd already included the systemd-nspawn tool as a more powerful version of chroot(1), primarily inteded for use in development, experimenting, debugging, instrumentation, testing and building of software. With Fedora 19 we want to make nspawn considerably more useful, so that it can easily be used to start containers capable of booting up a complete and unmodified Fedora distribution inside as normal system services. = Features/SystemdMessageCatalog = https://fedoraproject.org/wiki/Features/SystemdMessageCatalog Feature owner(s): Lennart Poettering <lennart at poettering dot net> Logging is essential for finding and tracking down system problems. Just finding and tracking them down however is seldom enough to actually get them fixed. With Journal Message Catalogs we want to link helpful meta information directly to many log messages applications generate, keyed off an ID identifying the type of message. This localized meta information can help the user to fix the problem, refer him to additional documentation, or even inform him where to get further help. = Features/SystemdResourceControl = https://fedoraproject.org/wiki/Features/SystemdResourceControl Feature owner(s): Lennart Poettering <lennart at poettering dot net> systemd already has support for assigning specific resources to system services using various configuration settings. With Fedora 19 we'd like to build on that, and add the ability for the admin to dynamically query the resource control parameters and change them at runtime.

1 0

Outage: Buildsystem Reboots and storage move 2013-01-30 22:00 UTC
by Kevin Fenzi 26 Jan '13

26 Jan '13

Outage: Buildsystem Reboots and storage move 2013-01-30 22:00 UTC There will be an outage starting at 2013-01-30 22:00 UTC, which will last approximately 2 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2013-01-30 22:00 UTC' Reason for outage: We will be updating servers and rebooting into the latest kernels. Additionally, we will be starting a backend ISCSI storage move for some machines. This move should complete in the background, but may result in some slower performance while it's running. Additionally, we will be upgrading the version of koji in use in our buildsystem to the latest upstream version. Affected Services: Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ GIT / Source Control Package Database - https://admin.fedoraproject.org/pkgdb/ Unaffected services: Ask Fedora - http://ask.fedoraproject.org/ BFO - http://boot.fedoraproject.org/ DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - http://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora People - http://fedorapeople.org/ Main Website - http://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ QA Services Secondary Architectures Spins - http://spins.fedoraproject.org/ Start - http://start.fedoraproject.org/ Torrent - http://torrent.fedoraproject.org/ Wiki - http://fedoraproject.org/wiki/ Unaffected Services: Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/3636 Contact Information: Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above.

1 0

Proposed F19 Feature: GLIBC 2.17
by Jaroslav Reznik 24 Jan '13

24 Jan '13

= Features/GLIBC217 = https://fedoraproject.org/wiki/Features/GLIBC217 Feature owner(s): Jeff Law <law(a)redhat.com> Switch GLIBC in Fedora 19 to GLIBC version 2.17. == Detailed description == GLIBC 2.17 was released at the end of 2012; we have been closely tracking the GLIBC 2.17 development code in Fedora Rawhide and addressing any issues as they arise. The proposed mass-rebuild with GCC 4.8 in February should also shake out any remaining problems with GLIBC's header files.

1 0

Proposed F19 Feature: NFStest
by Jaroslav Reznik 24 Jan '13

24 Jan '13

= Features/NFStest = https://fedoraproject.org/wiki/Features/NFStest Feature owner(s): Steve Dickson <steved(a)redhat.com> Provides a set of tools for testing either the NFS client or the NFS server, most of the functionality is focused mainly on testing the client. == Detailed description == NFStest provides a set of tools for testing either the NFS client or the NFS server, including the framework for developing more tests. These tools include the following: Process command line arguments Provide functionality for PASS/FAIL Provide test grouping functionality Provide multiple client support Logging mechanism Debug info control Mount/Unmount control Create files/directories Provide mechanism to start a packet trace Provide mechanism to simulate a network partition Support for pNFS testing Provide mechanism to automate packet trace inspection

1 0

Proposed F19 Feature: MEMSTOMP
by Jaroslav Reznik 24 Jan '13

24 Jan '13

= Features/MEMSTOMP = https://fedoraproject.org/wiki/Features/MEMSTOMP Feature owner(s): Jeff Law <law(a)redhat.com> Include the MEMSTOMP DSOs in Fedora 19 to enable developers to more quickly detect certain library calls which result in undefined behaviour due to overlapping memory arguments. == Detailed description == MEMSTOMP is a DSO which can be preloaded by an application to detect calls to library routines with overlapping memory arguments. Specifically MEMSTOMP will detect calls to the following routines with overalapping memory arguments: [w]memcpy, str[n]cat, wcs[n]cat, str[n]cpy, wcs[n]cpy, [w]mempcpy, memccpy, stp[n]cpy While valgrind can detect these cases, using a DSO such as MEMSTOMP can be significantly faster. The MEMSTOMP code utilizes GPLV2+ and LGPL3 code. The GPLV2+ code is limited to the backtrace code which is not thread safe and may need to be disabled/rewritten.

1 0

Proposed F19 Feature: systemd/udev Predictable Network Interface Names
by Jaroslav Reznik 23 Jan '13

23 Jan '13

= Features/SystemdPredictableNetworkInterfaceNames = https://fedoraproject.org/wiki/Features/SystemdPredictableNetworkInterfaceN… Feature owner(s): Kay Sievers <kay at redhat dot com> The udevd service has a long history of providing predicatable names for block devices and others. For Fedora 19 we'd like to provide the same for network interfaces, following a similar naming scheme, but only as fallback if not other solution such as biosdevname is installed or the administrator manually defined network interface names via udev rules or the old network scripts. == Detailed description == The classic naming scheme for network interfaces applied by the kernel is to simply assign names beginning with "eth0", "eth1", ... to all interfaces as they are probed by the drivers. As the driver probing is generally not predictable for modern technology this means that as soon as multiple network interfaces are available the assignment of the names "eth0", "eth1" and so on is generally not fixed anymore and it might very well happen that "eth0" on one boot ends up being "eth1" on the next. This can have serious security implications, for example in firewall rules which are coded for certain naming schemes, and which are hence very sensitive to unpredictable changing names. Starting with v197 systemd/udev can automatically assign predictable, stable network interface names for all local Ethernet, WLAN and WWAN interfaces. This is a departure from the traditional interface naming scheme ("eth0", "eth1", "wlan0", ...), but should fix real problems. This feature is about enabling this as default in Fedora, but only as a fallback if the user/administrator did not manually assign names to interfaces via udev rules, or via the old networking scripts, or if biosdevname is installed. For a longer discussion about this feature see the upstream documentation.

1 0

Proposed F19 Feature: Java 8
by Jaroslav Reznik 23 Jan '13

23 Jan '13

= Features/Java8TechPreview = https://fedoraproject.org/wiki/Features/Java8TechPreview Feature owner(s): Deepak Bhole <dbhole(a)redhat.com> Add a tech preview preview of the the upcoming version of Java (OpenJDK8) to Fedora 19. == Detailed description == The current Java implementation in Fedora comes from OpenJDK. Java 8 (and OpenJDK8) are tentatively scheduled for release in September 2013. Fedora 19 will most likely be out just a few months before that, and is therefore positioned to receive a tech preview version of the latest OpenJDK8 candidates.

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce January 2013