Fedora 26 Change Checkpoint: Completion deadline (testable)
by Jan Kurik
Greetings!
Today, on 2017-Feb-28, we have reached Fedora 26 Change
Checkpoint:Completion deadline (testable) [1].
At this point, all accepted changes [2] 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
achieved completeness.
Incomplete and non testable Changes [3] 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 [4]. I am going to ask FESCo to consider postponing
of this Checkpoint for these two Changes if these are approved.
[1] https://fedoraproject.org/wiki/Releases/26/Schedule
[2] https://fedoraproject.org/wiki/Releases/26/ChangeSet
[3] http://red.ht/2ltXbqk
[4] https://pagure.io/fesco/issue/1635#comment-350632
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
6 years, 9 months
Test instances for Fedora Package Maintainers
by Kevin Fenzi
Greetings.
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.
Please see:
https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintai...
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,
kevin
6 years, 9 months
F27 Self Contained Change: Bodhi Non-RPM Artifacts
by Jan Kurik
= Proposed Self Contained Change: Bodhi Non-RPM Artifacts =
https://fedoraproject.org/wiki/Changes/BodhiNonRPMArtifacts
Change owner(s):
* Randy Barlow <bowlofeggs AT fedoraproject DOT org>
Bodhi, the Fedora Updates System, should be able to process more than just RPMs.
== Detailed Description ==
As Fedora starts to deliver more than just RPMs and ISOs, we need a
way to handle delivering updates to these artifacts. Bodhi currently
handles this workflow for RPMs only, but we want to start using it for
other content, such as Docker containers, Flatpak apps, OSTrees, etc.
If it can be tagged in Koji, it should be accepted by Bodhi.
== Scope ==
* Proposal owners:
- Database model changes
- Masher modifications to the push process
- Web UI changes
- CLI modifications
- Unit tests
- Documentation
- Upstream tracker issue: https://github.com/fedora-infra/bodhi/issues/653
* Other developers:
- QA: Taskotron will need handle kicking off tests for non-RPM updates
- QA: Client-side updates-testing tools like fedora-easy-karma could
optionally be updated to detect these new artifacts
* Release engineering:
- We will need to ensure that the current signing process will work
with non-RPM content
- Ensure that the new content has a proper home in the directory structure.
- Releng ticket: #6660
- List of deliverables: N/A (not a System Wide Change)
* Policies and guidelines:
N/A (not a System Wide Change)
* 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
6 years, 9 months
F26 Self Contained Change: Python 3 C.UTF-8 locale
by Jan Kurik
= Proposed Self Contained Change: Python 3 C.UTF-8 locale =
https://fedoraproject.org/wiki/Changes/python3_c.utf-8_locale
Change owner(s):
* Charalampos Stratakis <cstratak AT redhat DOT com>
* Nick Coghlan <ncoghlan AT redhat DOT com>
The standalone Python 3.6 binary will automatically attempt to coerce
the C locale to C.UTF-8, unless the new PYTHONALLOWLOCALE environment
variable is set to 1.
== Detailed Description ==
When run under the C locale, Python 3 doesn't work properly on systems
where UTF-8 is the correct encoding for interacting with the rest of
the system. This proposed change for Python 3 packaged in Fedora
assumes the current locale is misconfigured when it detects that
"LC_TYPE" refers to the "C" locale, and in that case, prints a
warnings to stderr and forces the use of the C.UTF-8 locale instead.
To avoid unintended side effects, this change takes effect *solely*
when Python 3 is invoked by the user—nothing changes in cases where
CPython is used as a dynamically linked library. Also, an "escape
hatch" environment variable is provided to revert to the old behavior.
The effects of the problem for a popular CLI construction library are
explained on Armin Ronacher's blog:
http://click.pocoo.org/5/python3/#python-3-surrogate-handling
The problem is described in detail in PEP (Python Enhancement
Proposal) 538: https://www.python.org/dev/peps/pep-0538/
The PEP has no strong opposition upstream, but acceptance is held back
by considerations for other systems (e.g. those that do not have a
C.UTF-8 locale). These considerations do not apply for Fedora. We are
commited to follow upstream conversation and recommendations around
PEP 538. Also, we hope that testing this in Fedora will help upstream
find remaining distro integration issues.
The current version of the PEP specifically encourages backporting to
Python 3.6.0: https://www.python.org/dev/peps/pep-0538/#backporting-to-python-3-6-0
Check the Change Page for an example of the behaviour:
https://fedoraproject.org/wiki/Changes/python3_c.utf-8_locale#Detailed_De...
== Scope ==
* Proposal owners:
A patch will be backported to Fedora's Python 3.6 from the upstream
PEP 538 which targets Python 3.7. The patch that will be backported is
explicitly targeting Fedora, as the upstream equivalent one will have
to be compatible with Windows, macOS, Solaris etc. The Fedora specific
patch is provided by Nick Coghlan, a Python core developer.
* Release engineering:
No impact with release engineering
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
6 years, 9 months
F26 Self Contained Change: Arm Support In FMW
by Jan Kurik
= Proposed Self Contained Change: Arm Support In FMW =
https://fedoraproject.org/wiki/Changes/ArmSupportInFmw
Change owner(s):
* Martin Bříza <mbriza AT redhat DOT com>
Fedora Media Writer will gain the ability to write ARM images to SD
cards and other portable media.
== Detailed Description ==
With ARM (ARMv7A) being one of the primary architectures of Fedora, we
should support writing the images to bootable media for devices with
this architecture.
This means Fedora Media Writer will have to list the ARM images, offer
their download and be able to unpack them reliably (as they're shipped
LZMA-compressed - .xz). Memory card support should be improved,
especially in terms of reading drive information - many SD card
drivers report wrong names, sizes and media presence.
This will come along with many more features in FMW, such as
fullscreen screenshot preview, automatic FMW update check on Windows
and Mac, better reliability and performance improvements.
== Scope ==
* Proposal owners:
Implementation of this Change
* Other developers:
N/A (not a System Wide Change)
* Release engineering:
N/A
* List of deliverables:
N/A (not a System Wide Change)
* Policies and guidelines:
N/A (not a System Wide Change)
* 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
6 years, 9 months
F27 System Wide Change: No More Alphas
by Jan Kurik
= Proposed System Wide Change: No More Alphas =
https://fedoraproject.org/wiki/Changes/NoMoreAlpha
Change owner(s):
* Dennis Gilmore <dennis AT ausil DOT us>
* Adam Williamson <awilliam AT redhat DOT com>
Fedora will no longer produce Alpha releases.
== Detailed Description ==
By gating Rawhide builds from landing in the compose and gating the
publication of composes on automated test results we will ensure
Rawhide will always be at Alpha quality. This will make it more
generally useful to people as a daily driver and development platform,
and mean we no longer need to go through the process of building,
testing and shipping Alpha releases. The initial testing will be
ensuring that a package is installable and that it does not break
existing packages installation. Over time we can enable extra testing
to gate the build going into rawhide. Builds will land in the
buildroot to be built against before they make it to the compose.
== Scope ==
* Proposal owners:
rearrange the koji tag and target structure, have the testing in
place, setup processes to move builds in koji when they meet gating
criteria. The changes would start to be implemented in rawhide shortly
after branching Fedora 26
* Other developers:
Pay attention to new notifications and act when necessary
* Release engineering:
https://pagure.io/releng/issue/6621
* List of deliverables:
This change removes a milestone and all associated deliverables
* Policies and guidelines:
As there is no more Alpha we will need to update the guidelines to
have changes be completed for Beta. We will likely want to add a new
checkpoint for change implementation that currently needs to be
checked at Alpha
* 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
6 years, 9 months
F26 Self Contained Change: libpinyin 2.0
by Jan Kurik
= Proposed Self Contained Change: libpinyin 2.0 =
https://fedoraproject.org/wiki/Changes/libpinyin2.0
Change owner(s):
* Peng Wu <pwu AT redhat DOT com>
libpinyin 2.0 feature with multiple sentence candidates.
== Detailed Description ==
Now libpinyin provides 1-3 sentence candidates instead of one sentence
candidate, which will greatly improve the guessed sentence correction
rate.
== Scope ==
* Proposal owners:
- implements multiple sentence candidates feature.
- fixes bug or memory leak.
* Other developers:
N/A
* Release engineering:
N/A
* Policies and guidelines:
N/A
* Trademark approval:
N/A
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
6 years, 9 months
[Guidelines change] Changes to the packaging guidelines
by Jason L Tibbitts III
Here are the recent changes to the packaging guidelines.
-----
The systemd section of the scriptlet guidelines was updated to indicate
situations where the %systemd_ordering macro may be used instead of
%systemd_requires.
* https://fedoraproject.org/wiki/Packaging:Scriptlets#Systemd
* https://fedorahosted.org/fpc/ticket/644
-----
The guidelines for replacing existing packages have been updated with
mention of the "fedora-obsolete-packages" package:
* https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_...
* https://apps.fedoraproject.org/packages/fedora-obsolete-packages/overview/
* https://fedorahosted.org/fpc/ticket/645
-----
The guidelines for systemd scriptlets were updated with mention of the
macros to be used for systemd user units.
* https://fedoraproject.org/wiki/Packaging:Scriptlets#Systemd
* https://fedorahosted.org/fpc/ticket/647
-----
The SourceURL guidelines were updated to reflect a simpler method for
downloading tagged releases from Github.
* https://fedoraproject.org/wiki/Packaging:SourceURL#Git_Tags
* https://fedorahosted.org/fpc/ticket/651
-----
The Tags and Sections section of the main guidelines was modified to
use "SHOULD" and "MUST" language throughout, and to either discourage
or prohibit the use of certain tags and sections. The section is short,
so I've included it below.
"
* The Copyright:, Packager:, Vendor: and PreReq: tags MUST NOT be used.
* The BuildRoot: tag and %clean section SHOULD NOT be used.
* The contents of the buildroot SHOULD NOT be removed in the first line
of %install.
* The Summary: tag value SHOULD NOT end in a period.
* The Source: tags document where to find the upstream sources for the
package. In most cases this SHOULD be a complete URL to the upstream
tarball. For special cases, please see the SourceURL Guidelines.
* The Group: tag is unnecessary.
"
* https://fedoraproject.org/wiki/Packaging:Guidelines#Tags_and_Sections
* https://fedorahosted.org/fpc/ticket/652
-----
The File Permissions section was cleaned up somewhat, to use slightly
cleaner grammar, use "SHOULD" and "MUST" throughout and to remove
redundant information. In addition, the following sentence was added:
"The %defattr directive in the %files list SHOULD ONLY be used when
setting a non-default value, or to reset to the default value after
having set a non-default value."
* https://fedoraproject.org/wiki/Packaging:Guidelines#File_Permissions
* https://fedorahosted.org/fpc/ticket/652
-----
The Python Egg guidelines were update to better match current Python
packaging and to mention the %py*_install_egg macros.
* https://fedoraproject.org/wiki/Packaging:Python_Eggs
* https://fedorahosted.org/fpc/ticket/663
-----
The example spec in the Python guidelines was modified to correspond to
the usual, "python3 is default" case where versioned executables are not
installed.
* https://fedoraproject.org/wiki/Packaging:Python
* https://fedorahosted.org/fpc/ticket/672
-----
The guidelines for using Alternatives have been better indicate the
situations where alternatives are and are not appropriate.
* https://fedoraproject.org/wiki/Packaging:Alternatives
* https://fedorahosted.org/fpc/ticket/673
-----
The guidelines for per-product configuration have been updated to allow
copying the config file instead of mandating symlinking and to specify
the location where the variant configurations should be stored.
* https://fedoraproject.org/wiki/Packaging:Per-Product_Configuration
* https://fedorahosted.org/fpc/ticket/675
6 years, 9 months