Self contained changes for Fedora 26 release.
[https://fedoraproject.org/wiki/Changes/BIND_9.11 BIND version 9.11 ] [[br]] BIND (Berkeley Internet Name Domain) version 9.11 is the latest stable major update of the widely used DNS server. Besides new features, some settings defaults have changed since the previous major version (9.10). [[br]] - [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/65KNKXAYZU2Y63YB26A5JNV6VHJS54VX/ Announcement od devel-announce@ list] (on 2016-Oct-03) [[br]] - [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/65KNKXAYZU2Y63YB26A5JNV6VHJS54VX/#65KNKXAYZU2Y63YB26A5JNV6VHJS54VX Discussion on devel@ list]
[https://fedoraproject.org/wiki/Changes/OpenSSH_Crypto_Policy OpenSSH Crypto Policy (Client)] [[br]] OpenSSH client will follow system-wide crypto policies already followed by other cryptographic libraries and tools. It will allow to use different security levels defined system-wide. [[br]] - [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/3367AHINT7H24HB4FPG52JAUEXX6L7BP/ Announcement od devel-announce@ list] [[br]] - [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/3367AHINT7H24HB4FPG52JAUEXX6L7BP/#3367AHINT7H24HB4FPG52JAUEXX6L7BP Discussion on devel@ list]
Both the above changes got approved as
AGREED: self contained changes approved (+5,0,0) (nirik, 16:22:45)
let's keep this open as I can see few more changes may get added here for their approval next week.
Self contained Changes for the FESCo meeting on 2016-Oct-21:
I'm fine with Odoo but I'll echo my usual "not sure this is a Change"
Isn't this kind of exactly why we changed the name from "Features" to "Changes"? It's providing a set of things we might want to market.
That said, I'm not sure Fedora's users will necessarily care about this.
I'm fine with Odoo but I'll echo my usual "not sure this is a Change" Isn't this kind of exactly why we changed the name from "Features" to "Changes"? It's providing a set of things we might want to market.
No, the opposite. We changed to Changes because people were using "Features" as marketing material when it was never intended to be used that way. FESCo is not a marketing focused body, and there needs to be other ways to get things marketed outside of FESCo.
That speaks to my point. FESCo has NO idea what users will care about and this should be taken up with the Fedora marketing team.
Self contained Changes for the FESCo meeting on 2016-Oct-21: Odoo Odoo is the world's easiest all-in-one management software. It includes hundreds of integrated business apps: CRM, Accounting, Inventory, Marketing, eCommerce, Project Management, HR, MRP, etc. * Announcement od devel-announce@ list * Discussion on devel@ list
Odoo Odoo is the world's easiest all-in-one management software. It includes hundreds of integrated business apps: CRM, Accounting, Inventory, Marketing, eCommerce, Project Management, HR, MRP, etc. * Announcement od devel-announce@ list * Discussion on devel@ list
This was agreed as FESCo that it should not be a Change but it is absolutely welcome in the distro.
Just a note to the Odoo Change: I marked the wiki page as ChangeAcceptedF26 to indicate it goes to the release. However, I have not created tracking bug and I have not even put this to the F26 ChangeSet page.
Self contained Changes for the FESCo meeting on 2016-Oct-28:
Blivet-GUI in Anaconda Add blivet-gui as an alternative option for storage configuration in Anaconda Installer. - Announcement od devel-announce@ list - Discussion on devel@ list
I'm ambivalent here. As long as the addition is truly an addition and not something that requires users to relearn everything again, it seems like a win.
+1 from me here. :cruise_ship:
I'm +1, but it is past the contingency deadline already.
I'm +1, but it is past the contingency deadline already. This is for Fedora 26, not 25.
I'm +1
+1 for "Blivet-GUI in Anaconda" Change
I'm +1 for this Anaconda Blivet-GUI change.
+1 Anaconda Blivet-GUI change.
Anaconda Blivet-GUI change is now approved based on above +6 votes here.
Self contained Changes for the FESCo meeting on 2016-Nov-18:
Module Build Service We will deploy an instance of the Module Build Service to production in Fedora Infrastructure. Other teams will use this service to produce some "modular" content for the Fedora 26 release.
Modular Compose For Fedora 26, we would like to modify the compose tools (pungi) to produce an additional experimental variant, derived from modules built in the Module Build Service.
Self contained Changes for the FESCo meeting on 2016-Nov-18: Module Build Service We will deploy an instance of the Module Build Service to production in Fedora Infrastructure. Other teams will use this service to produce some "modular" content for the Fedora 26 release.
I asked questions on this and got 0 replies. It would be nice if someone bothered to answer my questions.
Announcement od devel-announce@ list Discussion on devel@ list Modular Compose For Fedora 26, we would like to modify the compose tools (pungi) to produce an additional experimental variant, derived from modules built in the Module Build Service. Announcement od devel-announce@ list Discussion on devel@ list
Announcement od devel-announce@ list Discussion on devel@ list
Apologies Josh, I didn't see it hit the list. My responses are there now.
AGREED: Modularity Changes are approved provided that they are emended to say that policies must b in place before restrictions are lifted (+1: 6, -1: 0, +0: 0) (maxamillion, 16:40:57)
Self contained Changes for the FESCo meeting on 2016-Dec-02:
Java/OpenJDK enforces the system-wide crypto policy As it is now, the System-wide crypto policy in F25 is enforced by the OpenSSL, GnuTLS and NSS TLS libraries. To harmonize crypto across all applications in Fedora, including the Java ones, OpenJDK is enhanced to respect the settings of the system-wide crypto policy as well.
Self contained Changes for the FESCo meeting on 2016-Dec-09:
Zend Framework 3 Update Zend Framework to latest version 3. Fedora 24 provides Zend Framework 2.5 (Change wrangler note: Fedora 25 provides ZF version 2.5.3), which is a transition version.
I'm +1 to Zend Framework 3
2016-12-09 FESCo Meeting: AGREED: Approve F26 Self Contained Change Java Security Policy (+1: 5, -1: 0, +0: 0)
2016-12-09 FESCo Meeting: AGREED: F26 Self Contained Change - Zend Framework 3 (+1: 6, -1: 0, +0: 0)
Self contained Changes for the next FESCo meeting.
Authconfig Cleanup Removal of obsolete and unmaintainable code from Authconfig such as the support for configuring Hesiod and the authconfig GTK2 based GUI and TUI.
In the 2016-Dec-16 FESCo meeting, the "Authconfig Cleanup" self-contained change was approved.
@jsmith changed the status to Closed
Closed
Golang buildmode PIE Change default build mode of golang in Fedora packaging macros to buildmode=pie, which results in packages using them to produce Position Independent Executables. Another part of the change is to pass the Fedora hardened linker flags to the external linker(regular system linker). In result reducing exploit-ability of binaries.
Fontconfig cache directory change The fontconfig cache files are placed onto /var/cache/fontconfig now. this seems incompatible with the ostree model. so this is a proposal to move it to /usr/lib/fontconfig/cache.
@jkurik changed the status to Open
Open
I'm +1 on the Golang change, and -1 on the Fontconfig cache directory change. (It doesn't seem right to me for a cache to live under /usr/lib.)
The Golang PIE change was discussed in the last meeting. There's an open question on performance impact. It would be good to at least have some token numbers.
From today's FESCo meeting:
Base Runtime We will deliver the first release of Base Runtime, a module providing base operating system features that application level modules can build and depend on. This module will be the foundation of the new modular Fedora 26 Server release.
@ausil changed the status to Closed
I had a long conversation with Colin Walters today regarding the placement of the fontconfig cache. I will attempt to summarize here and then make my recommendation.
The current behavior is that whenever a new RPM package is installed that places a font in /usr, the %post scripts will execute /usr/bin/fc-cache to update the "fontconfig cache". Unlike a traditional cache, this is more like an index of capabilities and functionality and remains unchanged except when installing or removing a font. (Meaning that it does not vary with system usage or other runtime activity.)
/usr/bin/fc-cache
The location of the fontconfig cache in /var is problematic for the OSTree model, because it is effectively static data that must be kept in sync with the contents of /usr. In OSTree, /var is not naturally modified when switching between trees. As such, since the data is not really variable, the OSTree maintainers feel that it would make more sense for the fontconfig indices to live in /usr instead of /var, where they can be pregenerated as part of the OSTree tree creation and then delivered as part of the atomic update (or rollback).
The major disagreement on the original BZ appears to stem mostly from the poorly-chosen word "cache". It is an extremely loose definition of the word "cache" (which normally implies aging, cache-invalidation and other highly-variable activities). In the case of fontconfig, the data does not vary at all except when new fonts are installed or removed and this requires a manual or rpm-driven action to call /usr/bin/fc-cache. I suspect that we would have had far less resistance if it was clearly referred to as an "index" rather than a "cache" (which it far more closely reflects).
I will point out that there are at least two existing precedents for keeping such indices in /usr:
uname -r
It is my primary recommendation that the fontconfig cache be moved to /usr/lib/fontconfig/cache and further treated as static data. I would also like to recommend that FESCo open a conversation with Red Hat's Open Source and Standards group about discussing a clarification in the FHS to describe such index-like caches and have this expressly added to the acceptable uses of /usr, to avoid future debates on this same topic.
Self contained Changes for the next FESCo meeting:
Transdiff Often even after 100% translation in Zanata, it sometimes happens that a few packages do not have the latest translations in Fedora. This results in a poor localization experience. Transdiff is a Python tool to run on installations for tracking translations with project upstream and generate diff reports.
Automated AMI test and release We will test the AMI image we build on one single region using the same tests used in Vagrant/local Autocloud testing, and if the tests pass, then only the AMI will be uploaded to all the regions and released.
LXQt Spin A Fedora Spin providing the LXQt desktop environment.
Docker Overlay 2 Change the default Docker Storage to use OverlayFS via the overlay2 driver, for better performance.
Making sudo pip Safe (Again) At the present time, running sudo pip3 in Fedora is not safe. Pip shares its installation directory with dnf, can remove dnf-managed files and generally break the Python 3 interpreter. We propose a series of measures that will make it safe to use.
NetworkManager 1.8 Update to NetworkManager to version 1.8.
I'm +1 to Transdiff, LXQt Spin, Docker Overlay 2, and Network Manager changes.
I'm +0 on the "sudo pip" proposal -- I'm not completely against it, but I do have some concerns about assuming what might be in /usr/local.
I'm fine with everything except the sudo pip change. There are open questions on the list that don't seem to have been answered. I suggest we defer until they are answered.
(I'll note I'm somewhat opposed to introducing new spins in general, but I have no specific concerns around LXQt itself.)
* #1635 F26 Self Contained Changes (sgallagh, 16:20:41) * transdiff Change Proposal has been deferred to F27 (sgallagh, 16:23:33) * AGREED: FESCo approves LXQt spin, Docker Overlay 2 and NetworkManager 1.8 (+6, 0, -0) (sgallagh, 16:25:20) * FESCo has unanswered questions about the sudo pip proposal and will discuss them on devel@ (sgallagh, 16:26:01)
@sgallagh changed the status to Closed
Anaconda LVM RAID Use LVM RAID instead of LVM of top of MD RAID in the Anaconda installer.
Container Minimal Image Produce a new container image that contains as little as possible, but also still provides the ability to install packages from dnf repositories.
LDC 1.1.0 Update LDC to 1.1.0 in Fedora 26.
Replace Coolkey with OpenSC There are more PKCS#11 libraries supporting the same smart cards in the system. For the next releases, we would like to promote OpenSC as a default PKCS#11 provided in place where Coolkey driver is used these days, which will extend a list of supported smart cards and make use of the most of the OpenSC.
Re: Anaconda LVM RAID, I mentioned it in the devel@ thread a couple times, it's a net regression if the device failure notification in GNOME Shell is thwarted by this change proposal. I think the change owners need to confirm if failure notifications still happen with LVM RAID; and if not, what their plan is to keep that functionality. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ZWPQ2YQPQ5NNM6GDPWRQXDXCGWASLGT7/ https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/LKICAIT5JESLGSO7NHQUHBW6IJC5TZAN/
The GNU C Library version 2.25 Switch glibc in Fedora 26 to glibc version 2.25
Metadata Update from @maxamillion: - Issue untagged with: meeting
Docker SDK for Python, version 2 Add new version of "Docker SDK for Python" to Fedora. This obsoletes existing python-docker-py package.
libpinyin 2.0 libpinyin 2.0 featuring multiple sentence candidates
From the FESCo meeting minutes:
Arm Support In FMW Fedora Media Writer will gain the ability to write ARM images to SD cards and other portable media.
Python 3 C.UTF-8 locale Force the C.UTF-8 locale when Python 3 is run under the C locale.
Metadata Update from @jkurik: - Issue tagged with: meeting
As the FESCo meeting on 2017-Mar-03 was cancelled and on 2017-Mar-07 there is going to be Alpha freeze, I suggest to postpone the last two Self Contained Changes (Arm Support In FMW, Python 3 C.UTF-8 locale) to the next, Fedora 27, release.
These were both approved for F26 during last meeting:
Metadata Update from @rathann: - Issue untagged with: meeting
I do not expect there will be more Self-Contained Changes for FESCo review, so I am closing this ticket. Thank you FESCo for all the reviews.
Metadata Update from @jkurik: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.