devel-announce August 2016

devel-announce@lists.fedoraproject.org

5 participants
9 discussions

Announcing the release of Fedora 25 Alpha!
by Dennis Gilmore 30 Aug '16

30 Aug '16

The Fedora Project is pleased to announce the immediate availability of the Fedora 25 Alpha, an important milestone on the road to our Fedora 25 release in November. Download the prerelease from our Get Fedora site: * https://getfedora.org/en/workstation/prerelease/ * https://getfedora.org/en/server/prerelease/ * https://getfedora.org/en/cloud/prerelease/ Or, check out one of our popular variants: * https://spins.fedoraproject.org/prerelease * https://labs.fedoraproject.org/prerelease * https://arm.fedoraproject.org/prerelease == Alternative Architectures == We are also simultaneously releasing the F25 Alpha for Power64 and 64-bit ARM (AArch64). These are available from: https://download.fedoraproject.org/pub/fedora-secondary/releases/test/ 25_Alpha/ == What is the Alpha release? == The Alpha release contains all the features of Fedora 25's editions in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When these bugs are fixed, we make a Beta release available. A Beta release is code-complete and bears a very strong resemblance to the third and final release. The final release of Fedora 25 is expected in November. If you take the time to download and try out the Alpha, you can check and make sure the things that are important to YOU are working. Every bug you find and report doesn't just help you, it improves the experience of millions of Fedora users worldwide! Together, we can make Fedora rock-solid. We have a culture of coordinating new features and pushing fixes upstream as much as we can, and your feedback improves not only Fedora, but Linux and Free software as a whole. * https://fedoraproject.org/wiki/Releases/25/Schedule == Issues and Details == Since this is an alpha release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the mailing list or in #fedora-qa on Freenode. As testing progresses, common issues are tracked on the Common F25 Bugs page. * https://fedoraproject.org/wiki/Common_F25_bugs For tips on reporting a bug effectively, read "how to file a bug report". * https://fedoraproject.org/wiki/How_to_file_a_bug_report == Release Schedule == The full release schedule is available on the Fedora wiki: * https://fedoraproject.org/wiki/Releases/25/Schedule The current schedule calls for a beta release towards the middle of October, and the final release in November. Be aware that these dates are development targets. Some projects release on a set date regardless of feature completeness or bugs; others wait until certain thresholds for functionality or testing are met. Fedora uses a hybrid model, with milestones subject to adjustment. This allows us to make releases with new features and newly- integrated and updated upstream software while also retaining high quality. Enjoy Fedora Release Engineering (Dennis, Peter, Kevin, Mohan, Adam, Randy)

1 0

Fedora 25 Alpha status is GO, release on August 30, 2016
by Jaroslav Reznik 25 Aug '16

25 Aug '16

At the second Fedora 25 Alpha Go/No-Go Meeting [1][2] that just ended, it has been agreed by QA, Release Engineering and Development to go live with the Fedora 25 Alpha. Fedora 25 Alpha release will be publicly available on August 30, 2016. Meeting details can be seen here: [1] Minutes: https://meetbot.fedoraproject.org/fedora-meeting-2/2016-08-25/f25-alpha-go_… [2] Log: https://meetbot.fedoraproject.org/fedora-meeting-2/2016-08-25/f25-alpha-go_… Thanks everyone! Jaroslav

1 0

Fedora 25 Alpha Release Readiness Meeting, Thursday, August 18 @ 19:00 UTC
by Jan Kurik 19 Aug '16

19 Aug '16

Join us on irc.freenode.net in #fedora-meeting for the Fedora 25 Alpha Release Readiness Meeting meeting. The meeting is going to be held on Thursday, August 18, 2016 19:00 UTC. Please check the [FedoCal] link for your time zone. We will meet to make sure we are coordinated and ready for the Alpha release of Fedora 25 on Tuesday, August 23nd, 2016. Please note that this meeting is going to be held even if the release is delayed at the Go/No-Go meeting on the same day two hours earlier. You may received this message several times, but it is by purpose to open this meeting to the teams and to raise awareness, so hopefully more team representatives will come to this meeting. This meeting works best when we have representatives from all of the teams. [FedoCal] https://apps.fedoraproject.org/calendar/meeting/4486/ More information available at: https://fedoraproject.org/wiki/Release_Readiness_Meetings Thank you for your support and Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 1

[Guidelines change] Changes to the packaging guidelines
by Jason L Tibbitts III 18 Aug '16

18 Aug '16

Here are the recent changes to the packaging guidelines. ----- The Filesystem Layout section of the guidelines was simplified and outdated information was removed. * https://fedoraproject.org/wiki/Packaging:Guidelines * https://fedoraproject.org/wiki/Packaging:Guidelines#Filesystem_Layout * https://fedorahosted.org/fpc/ticket/623 ----- The outdated section restricting dependencies between /bin and /usr has been removed. * https://fedoraproject.org/wiki/Packaging:Guidelines * https://fedoraproject.org/wiki/Packaging:Guidelines#Binaries_in_.2Fbin_and_… (now deleted) * https://fedorahosted.org/fpc/ticket/624 ----- A set of guidelines for GAP packages has been added. * https://fedoraproject.org/wiki/Packaging:GAP * https://fedorahosted.org/fpc/ticket/625 ----- A section has been added to the guidelines which documents the procedure for deviation from those guidelines. Work will now begin to clarify the language in existing guidelines into the usual SHOULD and MUST categories to help reduce confusion surrounding the "strength" of guidelines. * https://fedoraproject.org/wiki/Packaging:Guidelines#General_Exception_Policy * https://fedorahosted.org/fpc/ticket/633 ----- Due to the addition of RPM file triggers, the scriptlet guidelines have been amended to indicate that some scriptlets should not be used in F24+. Specifically: gsettings schemas, gdk-pixbuf loaders, gtk+ 3 modules, gio modules and mimeinfo. Also, update-desktop-database should not be used as of Fedora 25. * https://fedoraproject.org/wiki/Packaging:Scriptlets * https://fedorahosted.org/fpc/ticket/636 ----- The review process document has been amended to note possible exceptions, and to indicate that review is not needed in certain situations where a different version of an existing package is being added. * https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Package_Review_Pr… * https://fedorahosted.org/fpc/ticket/637 ----- Corrected the suggest source URL for tarballs hosted on pypi to use https://files.pythonhosted.org * https://fedoraproject.org/wiki/Packaging:Python#Example_common_spec_file * https://fedoraproject.org/wiki/Packaging:SourceURL#Python_Packages_.28pypi.… * https://fedorahosted.org/fpc/ticket/640 ----- The running of system daemons as the "nobody" user has been forbidden. * https://fedoraproject.org/wiki/Packaging:Guidelines#Users_and_Groups * https://fedorahosted.org/fpc/ticket/642

1 0

Fedora 25 Alpha status is NO-GO
by Jan Kurik 18 Aug '16

18 Aug '16

Release status of the Fedora 25 Alpha Go/No-Go Meeting is NO-GO. Due to missing RC and present blockers [1] in the Fedora 25 Alpha, the decision is to slip the Fedora 25 Alpha release for one week. There is going to be one more Go/No-Go meeting the next Thursday, August 25th, 2016 at 5:00PM UTC to verify we are ready for the release. For more information please find the logs or minutes from the meeting [2][3]. [1] https://qa.fedoraproject.org/blockerbugs/milestone/25/alpha/buglist [2] https://meetbot.fedoraproject.org/fedora-meeting/2016-08-18/f25-alpha-go_no… [3] https://meetbot.fedoraproject.org/fedora-meeting/2016-08-18/f25-alpha-go_no… Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

F26 System Wide Change: Python 3.6
by Jan Kurik 16 Aug '16

16 Aug '16

= Proposed System Wide Change: Python 3.6 = https://fedoraproject.org/wiki/Changes/Python3.6 Change owner(s): * Charalampos Stratakis <cstratak AT redhat DOT com > * Dominika Krejči <dkrejci AT redhat DOT com> * Lumír Balhar <lbalhar AT redhat DOT com> * Michal Cyprian <mcyprian AT redhat DOT com> * Miro Hrončok <mhroncok AT redhat DOT com> * Petr Viktorin <pviktori AT redhat DOT com> * Tomáš Orsava <torsava AT redhat DOT com> Update the Python 3 stack in Fedora from Python 3.5 to Python 3.6. == Detailed Description == Python 3.6 adds numerous features and optimizations. See the upstream notes at Features for 3.6 and What's new in 3.6 == Scope == Proposal owners: * All the downstream patches will need to be reviewed and then rebased or dropped accordingly. Since some patches are arch specific, they will need to be reviewed for their respective architecture. * Most of the python packages requiring Python 3, should be compatible with Python 3.6. Some incompatible changes and how to port code to Python 3.6 can be seen here: Porting to Python 3.6 * Currently there are 1500 packages in Fedora 26 that either BuildRequires or Requires Python 3, and with the continuing porting efforts, the number gets higher every day. * After change is accepted, and a release candidate of Python 3.6 is available, it will be built for F26. * Release Milestones for Python 3.6: https://www.python.org/dev/peps/pep-0494/#schedule * There is already a copr repo with the third alpha of Python 3.6 (Python-3.6.0a3) which can be enabled by: dnf copr enable cstratak/python-3.6 Other developers: *Owners of packages that fail to rebuild during the mass rebuild will be asked, using bugzilla, to fix or remove their packages from the distribution. If any issues appear, they should be solvable either by communicating with upstreams first and/or applying downstream patches. Also the package maintainers should have a look at: Porting to Python 3.6. And python-maint team will be available to help with fixing issues. Release engineering: * Packages will be rebuilt during mass rebuild. If there is no mass rebuild for whatever reason, a targeted mass rebuild for all python packages will be required. Policies and guidelines: None Trademark approval: N/A (not needed for this Change) -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

Fedora 25 Alpha Go/No-Go Meeting, Thursday, August 18 @ 17:00 UTC
by Jan Kurik 15 Aug '16

15 Aug '16

Join us on irc.freenode.net in #fedora-meeting for this important meeting, wherein we shall determine the readiness of the Fedora 25 Alpha. The meeting is going to be held on Thursday, August 18, 2016 at 17:00 UTC. Please check the [FedoCal] link for your time zone. 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. Release Candidate (RC) availability and good QA coverage are prerequisites for the Go/No-Go meeting. If you have any bug on the list, please help us with Alpha release. If we won't be ready by Thursday, we will use this meeting to review blockers and decide what to do. For more details about this meeting please follow the [GoNoGoMeeting] link. In the meantime, please keep also an eye on the Fedora 25 Alpha Blocker list [AlphaBlockers]. [FedoCal] https://apps.fedoraproject.org/calendar/meeting/4485/ [AlphaBlockers] http://qa.fedoraproject.org/blockerbugs/milestone/25/alpha/buglist [GoNoGoMeeting] https://fedoraproject.org/wiki/Go_No_Go_Meeting Thank you in advance for your support. Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

Fedora 25 Alpha Freeze
by Mohan Boddu 08 Aug '16

08 Aug '16

Hi all, Today's an important day on the Fedora 25 schedule[1], with several significant cut-offs. First of all today is the Bodhi activation point [2]. That means that from now all Fedora 25 packages must be submitted to updates-testing and pass the relevant requirements[3] before they will be marked as 'stable' and moved to the fedora repository. Today is also the Alpha freeze[4]. This means that only packages which fix accepted blocker or freeze exception bugs[5][6] will be marked as 'stable' and included in the Alpha composes. Other builds will remain in updates-testing until the Alpha release is approved, at which point the Alpha freeze is lifted and packages can move to 'stable' as usual until the Beta freeze. Today is also the Software String freeze[7], which means that strings marked for translation in Fedora-translated projects should not now be changed for Fedora 25. Finally, today is the 'completion deadline' Change Checkpoint[8], meaning that Fedora 25 Changes must now be 'feature complete or close enough to completion that a majority of its functionality can be tested'. Regards Mohan Boddu [1] https://fedoraproject.org/wiki/Releases/25/Schedule [2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling [3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release [4] https://fedoraproject.org/wiki/Milestone_freezes [5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy [8] https://fedoraproject.org/wiki/Changes/Policy

1 0

REMINDER: Fedora 25 Alpha Freeze in one week (Tuesday 2016-Aug-09)
by Jan Kurik 01 Aug '16

01 Aug '16

Hi all, In one week, on Tuesday 2016-Aug-09, is an important day on the Fedora 25 schedule [1], with several significant cut-offs. First of all, it is the Bodhi activation point [2]. That means that from this day all Fedora 25 packages must be submitted to updates-testing and pass the relevant requirements [3] before they will be marked as 'stable' and moved to the fedora repository. At the same time there is also the Alpha freeze [4]. This means that only packages which fix accepted blocker or freeze exception bugs [5][6] will be marked as 'stable' and included in the Alpha composes. Other builds will remain in updates-testing until the Alpha release is approved, at which point the Alpha freeze is lifted and packages can move to 'stable' as usual until the Beta freeze. Finally, at the same day is also the Software String freeze [7], which means that strings marked for translation in Fedora-translated projects should not be changed for Fedora 25. Regards, Jan [1] https://fedoraproject.org/wiki/Releases/25/Schedule [2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling [3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release [4] https://fedoraproject.org/wiki/Milestone_freezes [5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce August 2016