The Fedora 24 Alpha for aarch64 is here, right on schedule for our planned June
final release. Download the prerelease from our Get Fedora site:
- Get Fedora 24 Alpha Server
What is the Alpha release?
The Alpha release contains all the features of Fedora 24'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 24 is expected in June.
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.
Under the hood, glibc has moved to 2.23. The update includes better
performance, many bugfixes and improvements to POSIX compliance, and
additional locales. The new library is backwards compatible with the
version of glibc that was shipped in Fedora 23, and includes a number
of security and bug fixes.
We've also updated the system compiler to GCC 6 and rebuilt all
packages with that, providing greater code optimization and catching
programming errors which had slipped past previous compilers.
In aarch64 golang 1.6 brings all the same golang functionality that
other architectures have enjoyed enabling all the features and apps
that are avaialble there such as docker.
- FreeIPA 4.3 (Domain Controller role) is included in Fedora 24. This
version helps streamline installation of replicas by adding a
replica promotion method for new installs. A new topology plugin has
also been added that automatically manages new replication segment
creation. An effective replica topology visualization tool is also
available in the webUI.
- NodeJS 4 in now available for aarch64. Earlier versions of nodejs have
been available on primary architectures for some time. With nodejs4 we
now bring all the functionality to aarch64 too.
- More packages have been removed from the default Server edition to
make the footprint of the default installation smaller.
Cloud and Docker
Not quite ready for Alpha both qemu cloud images and docker images will
be appearing for nightly Fedora 24 aarch64 composes starting next week.
All the docker pieces are already in place in Fedora 24 Alpha. The last
pieces of the infrastructure to build the nightly docker images are
almost live into production. There will be appropriate announcements
when they go live.
Issues and Details
This is an Alpha release. As such, 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
As testing progresses, common issues are tracked on the Common F24 Bugs
For tips on reporting a bug effectively, read "how to file a bug
The full release schedule is available on the Fedora wiki:
The current schedule calls for a beta release towards the beginning of May,
the final release in early June.
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.
devel-announce mailing list
Please see below for the log/minutes of the first Modularity WG meeting.
Please note, not terribly awesome at zodbot, so, forgot to #info or
whatever that we would table the "what to do and by when" discussion
until after the "how to do stuff" discussion. We ran out of time, so
that will be on the agenda for next meeting.
* roll call (langdon, 15:03:56)
* context setting (langdon, 15:07:12)
* LINK: https://fedoraproject.org/wiki/Modularization (langdon,
* modularization wiki page (langdon, 15:08:19)
* LINK: https://fedoraproject.org/wiki/Modularity_Working_Group
* modularity working group wiki page (langdon, 15:08:50)
* number of voting members (langdon, 15:12:47)
* number of voting members & term of service (langdon, 15:13:42)
* LINK: https://fedoraproject.org/wiki/Server/Governance_Charter
* ACTION: langdon to modify wiki page to show proposed governance and
then send to mailing list for approval (langdon, 15:29:55)
* when should the meetings be (langdon, 15:30:36)
* AGREED: meeting time is weekly on thursdays at 15h UTC (langdon,
* ACTION: langdon to update fedocal "correctly" (langdon, 15:35:11)
* what to deliver & when (langdon, 15:35:37)
* how to do stuff (langdon, 15:38:18)
* LINK: http://taiga.fedorainfracloud.org/project/langdon-modularity/
Modularity taiga board (sctw, 15:47:21)
* LINK: http://taiga.fedorainfracloud.org/ (langdon, 15:47:36)
* taiga deployment seems to work much better for you to go 1) login
once using fas; 2) ask someone to add you to modify the board/take
cards .. but pre-invite does not seem to work well (langdon,
* AGREED: agile-y approach, using taiga, potentially modifiable by the
WG voting members (langdon, 15:58:03)
* ACTION: wg needs to write up the details of the approach (langdon,
* ACTION: wg needs to solve how to demo (langdon, 15:58:44)
* to join the taiga project and take cards: 1) login in to taiga using
fas; 2) send email to langdon(a)fp.o with your *target* email address
for your me(a)fp.o acccount (langdon, 16:03:03)
* we have #fedora-modularization for discussion.. so please join us
there any time (langdon, 16:05:25)
Meeting ended at 16:07:28 UTC.
* langdon to modify wiki page to show proposed governance and then send
to mailing list for approval
* langdon to update fedocal "correctly"
* wg needs to write up the details of the approach
* wg needs to solve how to demo
Modularity Objective Lead
Michael, you make a very good point at
Our packaging guidelines really ought to mandate that *if* upstream
publishes GPG or PKCS#7/CMS signatures of source tarballs, then the
package *must* verify those signatures as part of %prep.
Do you want to put a draft together for approval by the packaging
It might be nice to provide some RPM macros to make that easier for
I've had a go at doing this for OpenConnect, in
It's a bit pointless there, since the tarballs tend to get uploaded to
Fedora from the same workstation I sign them on, sometimes *before*
they're uploaded to the FTP site. But it's still good practice, as you
rightly point out.
David Woodhouse Open Source Technology Centre
David.Woodhouse(a)intel.com Intel Corporation
First and foremost, I would like to point out that we have a modularity
calendar in fedocal. We will schedule meetings there and, likely,
send a note to devel@ for each meeting with an agenda, etc.
I would also like to formally invite the Fedora Base WG and Envs &
Stacks members to the new Modularity WG and hope to see them at the meeting.
I am proposing the following agenda for today, but am happy to take
edits here or during the meeting.
* intros, overview, context setting
* determine the number of voting members of the WG
* proposal to close nominations early as we likely have more than required
* discuss the best time for future, recurring meetings
* discuss "what to deliver" & planned delivery dates
* discuss approach for "doing work"
* assign people to update wiki with decisions
Modularity Objective Lead
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2016-03-31 16:00 UTC in #fedora-meeting-1 on
Local time information (via. rktime):
2016-03-31 09:00 Thu US/Pacific PDT
2016-03-31 12:00 Thu US/Eastern EDT
2016-03-31 16:00 Thu UTC <-
2016-03-31 17:00 Thu Europe/London BST
2016-03-31 18:00 Thu Europe/Paris CEST
2016-03-31 18:00 Thu Europe/Berlin CEST
2016-03-31 21:30 Thu Asia/Calcutta IST
2016-04-01 00:00 Fri Asia/Singapore SGT
2016-04-01 00:00 Fri Asia/Hong_Kong HKT
2016-04-01 01:00 Fri Asia/Tokyo JST
2016-04-01 02:00 Fri Australia/Brisbane EST
Links to all tickets below can be found at:
= Followups =
#topic #558 Application/Library distinction and package splitting
#topic #566 RPM file triggers
= New business =
#topic #610 Packaging guidelines: Check upstream tarball signatures
#topic #612 Python naming convention makes some Python tools unusable
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at:
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fpc,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.