Today, on 2017-Feb-28, we have reached Fedora 26 Change
Checkpoint:Completion deadline (testable) .
At this point, all accepted changes  should be substantially
complete, and testable. Additionally, if a change is to be enabled by
default, it must be enabled at Change Completion deadline as well.
Change tracking bug should be set to the MODIFIED state to indicate it
Incomplete and non testable Changes  will be reported to FESCo for
2017-Mar-03 meeting. Contingency plan for System Wide Changes, if
planned for Alpha (or in case of serious doubts regarding Change
completion), will be activated.
Side note: Currently we still have two Self-Contained Changes waiting
for FESco approval . I am going to ask FESCo to consider postponing
of this Checkpoint for these two Changes if these are approved.
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
I've just finished setting up a new group of test machine instances for
package maintainers in the Fedora Infrastructure Private Cloud.
They now include ppc64 and ppc64le instances.
(We hope to add aarch64 before too long).
These instances should be faster and closer to repositories than
previous test instances, and require no special ssh config to use.
for more details and access information on all the available instances.
These instances can help maintainers duplicate problems or gather
information from Fedora versions they may not have handy.
Hope they help,
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org
there seems to be a small number of nodejs-* packages that use a
hard-coded ExclusiveArch value instead of the %nodejs_arches macro or
they weren't rebuilt during the mass-rebuild.
^^ those might be false positives as mapnik is not available on big
endian platforms (ppc, ppc64, s390, s390x)
Could the nodejs team review and fix the packages? Or let me know they
can be all moved to %nodejs_arches and I will fix that.