Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 26
The meeting is going to be held on Thursday, July 6th, 2017 at 17:00
UTC. Please check the  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 the Final release. If we won't be ready by
Thursday, we will use this meeting to review blockers and decide what
In the meantime, please keep also an eye on the Fedora 26 Final
Blocker list .
For more details about this meeting please follow the  link.
As I will not be available for this meeting, Jaroslav Reznik <jreznik>
will be the moderator. Please contact Jaroslav in case of a need for
Thank you in advance for your support.
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Just a reminder, as the announcement was over a week ago, that tomorrow
is Fedora 26 Upgrade Test Day in #fedora-test-day on Freenode!
Please come out and help test if you can. Thanks!
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
test-announce mailing list -- test-announce(a)lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave(a)lists.fedoraproject.org
As the modularity work starts to enter Fedora with the Fedora 27
release, a typical Change Proposal did not seem to do justice on
capturing the moving parts and dependencies for the work to successfully
land. As a result, this document attempts to capture, at a high level,
the goals and deliverables for F27. We are also providing links to the
details to most aspects. Some of the details are still in progress and
will change over the F26 lifecycle (e.g. which modules will be included
for F27 Server).
The Modularity and Server Working Groups plan, with the help of many
other groups in Fedora, to deliver a fully modularized version of the
Fedora Server Edition. As an equal and complementary goal, the tooling
for module creation/development, deployment and automatic testing will
be as simple and automated as possible.
- Although modularity allows for lifecycle changes, there is no plan
for anything besides the normal 13 month lifecycle at this point.
- Available content as modules will be less than a typical Server release
- Only components that are a part of a module will be available
- Any RPM that is a part of module will be available to be
installed directly or in addition to the “install profile” install of
- Infrastructure Changes/Improvements:
- Bodhi: changes to support updating & tracking modules:
- Arbitrary branching: enables modules to versions bound to
something other than Fedora release number:
- Bugzilla & ABRT module-awareness are still in progress
- COPR: support for building modules has been added and will be
improved over the F26 cycle
- Automation (Freshmaker)
- On Demand Compose Service (for testing and container rebuilds)
- Greenwave: for policy/gating in Bodhi. User interactions
take place in Bodhi.
- Installation & System Management
- Anaconda: still in progress
- DNF: Work underway to support modules, additional features need
to be added. Please report comments/features/bugs in the [*normal
- Gnome Software: still in progress
- Host & Platform module(s): Base components that provide the
“operating system” aspects of Modular Fedora:
- Application modules ([*Content
- TBD language modules (1 or more versions each)
- TBD database modules (1 or more versions each)
- TBD web server modules (1 or more versions each)
- TBD utility server modules (1 or more versions each)
- Applications as System Containers ([*Content
- TBD system integrated containers
- Module Guidelines and Processes:
- HowTos, Examples, and Tools for Modules:
BENEFITS FOR USERS
- Content available in multiple streams - good examples needed
- Software Collections done the right way - Languages, Databases
- No visible change to dnf/yum unless you want to select non-default
- Bodhi Changes [*Focus
- Freshmaker Focus doc
- ODCS Focus doc
- Branching Focus doc
Fedora Modularity Objective Lead
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org
as announced, yesterday I built nodejs-8.1.2 in rawhide.
Please, check that your packages work, especially native modules,
as there seem to be a few incompatibilities.
We also got new npm@5, which is said to be a little buggy.
I am trying to package the following from github for fedora. (Actually, I have been using my own RPM for years so it is hopefully not a major task).
Anyway, I wanted to ask how I should put the Source code from there
The source is at:
but that does not give me the version, etc number to build from the spec file.
So, what should I do?