The next Tuesday, on 2017-May-16, we will reach two important
milestones of the Fedora 26 release [1]:
== Change Checkpoint: 100% Code Complete Deadline [2] ==
* New accepted changes must be code complete, meaning all the code
required to enable to the new change is finished.
* The level of code completeness is reflected as tracker bug state
ON_QA. The change does not have to be fully tested by this deadline.
== Beta Freeze [3] ==
Only packages which fix accepted blocker or freeze exception bugs [4]
will be marked as 'stable' and included in the Beta composes. Other
builds will remain in updates-testing until the Beta release is
approved, at which point the Beta freeze is lifted and packages can
move to 'stable' as usual until the Final freeze.
[1] https://fedoraproject.org/wiki/Releases/26/Schedule
[2] https://fedoraproject.org/wiki/Changes/Policy
[3] https://fedoraproject.org/wiki/Milestone_freezes
[4] https://qa.fedoraproject.org/blockerbugs/milestone/26/beta/buglist
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: Arbitrary Branching =
https://fedoraproject.org/wiki/Changes/ArbitraryBranching
Change owner(s):
* Matt Prahl <mprahl AT redhat DOT com>
Tooling changes to support the new way of branching for Fedora 27.
== Detailed Description ==
To avoid maintaining multiple copies of this information, please read
the Arbitrary Branching Focus Document (updated May 3rd, 2017) in the
Factory2 space as a substitute for this document:
https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/ArbitraryBranc…
For further information, view this section of Ralph Bean’s
presentation at DevConf: https://youtu.be/5gqccjyjwFk?t=26m27s
== Scope ==
* Proposal owners:
We will do all of the work listed in the linked document.
* Other developers:
- We're relying on the infra team to get Pagure on top of dist-git.
- We're relying on releng to find any holes in our work plan and to
help us make decisions on how to solve bugs.
- No direct work should be required from the general packaging group
to support this Change.
* Release engineering:
https://pagure.io/releng/issue/6775
* List of deliverables:
Not affected
* Policies and guidelines:
- Packaging guidelines would change and would be updated after the
changes are implemented in staging.
* 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
There will be an outage starting at 2017-05-04 06:00 UTC, which will
last approximately 4 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2017-05-04 06:00 UTC'
Reason for outage:
We will be applying updates and rebooting the fedorainfracloud. This
will affect copr builds, frontend and backend as well as any other
applications hosted in the cloud.fedoraproject.org or
fedorainfracloud.org domains.
Affected Services:
* copr: frontend, backend and builds.
* *.fedorainfracloud.org and cloud.fedoraproject.org development and
test instances.
Contact Information:
Ticket Link:
https://pagure.io/fedora-infrastructure/issue/6026
Please join #fedora-admin or #fedora-noc on irc.freenode.net or add
comments to the ticket for this outage above.
There will be an outage starting at 2017-05-02 21:00UTC, which will
last approximately 4 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:
date -d '2017-05-02 21:00 UTC
Reason for outage:
We will be applying updates and rebooting servers into newer kernels.
Fedora build related services may be up or down during the outage window.
Affected Services:
* pkgs.fedoraproject.org
* koji
* koshei
* kojipkgs
* pkgdb
* bodhi / updates
* mdapi service
Services not listed are not affected by this outage.
Contact Information:
Ticket Link:
https://pagure.io/fedora-infrastructure/issue/6024
Please join #fedora-admin or #fedora-noc on irc.freenode.net or add
comments to the ticket for this outage above.