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)
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
= 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
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