devel-announce April 2018

devel-announce@lists.fedoraproject.org

9 participants
15 discussions

Fedora 28 Final status is GO
by Jan Kurik 26 Apr '18

26 Apr '18

The Fedora_28_RC_1.1 compose [1] is considered as GOLD and it is going to be shipped on 2018-May-01 as Fedora 28 Final release. For more information please check the meeting minutes [2] from the Go/No-Go meeting. [1] http://dl.fedoraproject.org/pub/alt/stage/28_RC-1.1/ [2] https://meetbot.fedoraproject.org/fedora-meeting-1/2018-04-26/f28-final-go-… Regards, Jan -- Jan Kuřík JBoss EAP Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

libicu upgrade to 61.1 with soname bump in rawhide/F29
by Eike Rathke 26 Apr '18

26 Apr '18

Hi, I'm upgrading libicu to 61.1 for rawhide, which as usual comes with a soname bump. I requested a side target f29-icu for the builds, I'll ask Pete Walter (who already did it for 60.1) to help with rebuilding the dependent packages, or another proven packager if he's not available. Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A Care about Free Software, support the FSFE https://fsfe.org/support/?erack

1 0

[Guidelines change] Changes to the packaging guidelines
by Jason L Tibbitts III 23 Apr '18

23 Apr '18

Here are the recent changes to the packaging guidelines. ----- A note was added to the Python guidelines indicating that the python2 stack may go away and that upstreams should be contacted about software not yet ported to python3. * https://fedoraproject.org/wiki/Packaging:Python#Python_Version_Support * https://pagure.io/packaging-committee/issue/753 ----- The Python guidelines now more clearly indicate that use of %{__python}, %{python_sitelib} and %{python_sitearch} is forbidden. * https://fedoraproject.org/wiki/Packaging:Python#Macros * https://pagure.io/packaging-committee/issue/745 ----- Information about the automatic shebang line checking and modification has been added to both the main guidelines and the Python guidelines. * https://fedoraproject.org/wiki/Packaging:Guidelines#Shebang_lines * https://fedoraproject.org/wiki/Packaging:Python#Multiple_Python_Runtimes * https://pagure.io/packaging-committee/issue/738 ----- The guidelines section relating to architecture support has been updated to reflect the current state of koji's support of ExclusiveArch:/ExcludeArch: in noarch packages. * https://fedoraproject.org/wiki/Packaging:Guidelines#Noarch_with_Unported_De… * https://pagure.io/packaging-committee/issue/751 ----- A guideline was added showing how to disable buildroot policy scripts for your package, if necessary: * https://fedoraproject.org/wiki/Packaging:Guidelines#BRP_.28BuildRoot_Policy… * https://pagure.io/packaging-committee/issue/749 ----- The Documentation section of the main guidelines was expanded to include information about reducing build dependencies by building documentation in a separate source package. * https://fedoraproject.org/wiki/Packaging:Guidelines#Documentation * https://pagure.io/packaging-committee/issue/715 ----- The AppData guidelines were updated to mention the %_metainfodir macro, which was added to cut down on the need for %if blocks in cross-distro specfiles. * https://fedoraproject.org/wiki/Packaging:AppData#app-data-validate_usage * https://pagure.io/packaging-committee/issue/752 Note that redhat-rpm-config/epel-rpm-macros packages supporting this are in updates-testing, but buildroot overrides are active so you can use the macro in Koji builds now. ----- The section on packaging additional RPM macros has been simplified significantly. * https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional… * https://pagure.io/packaging-committee/issue/601 Note that the epel-rpm-macros package supporting this in EPEL7 is in updates-testing, but a buildroot override is active so you can use the macro in Koji builds now.

1 0

Estonia Open-EID available again
by Germano Massullo 19 Apr '18

19 Apr '18

Hello, I am glad to announce that the Estonia Open-EID client software stack[1], has been unretired and updated to lastest version. To use it, simply install open-eid package. System reboot is recommended[2]. Best regards [1]: https://github.com/open-eid/ [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1545027

1 0

Fedora 28 Final Release Readiness Meeting on Thursday, April 26 @ 19:00 UTC
by Jan Kurik 19 Apr '18

19 Apr '18

Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 28 Final Release Readiness Meeting meeting. The meeting is going to be held on Thursday, April 26, 2018 at 19:00 UTC. Please check the [1] link for your time zone. We will meet to make sure we are coordinated and ready for the Final release of Fedora 28. Please note that this meeting is going to be held even if the release is delayed at the Go/No-Go meeting on the same day two hours earlier. You may received this message several times, but it is by purpose to open this meeting to the teams and to raise awareness, so hopefully more team representatives will come to this meeting. This meeting works best when we have representatives from all of the teams. For more information please check the [2] link. [1] https://apps.fedoraproject.org/calendar/meeting/9024/ [2] https://fedoraproject.org/wiki/Release_Readiness_Meetings Thank you for your support, Regards, Jan -- Jan Kuřík JBoss EAP Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

Fedora 28 Final release Go/No-Go Meeting on Thursday, April 26 @ 17:00 UTC
by Jan Kurik 19 Apr '18

19 Apr '18

Join us on irc.freenode.net in #fedora-meeting-1 for this important meeting, wherein we shall determine the readiness of the Fedora 28 Final. The meeting is going to be held on Thursday, April 26, 2018 at 17:00 UTC. Please check the [1] 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 Beta release. If we won't be ready by Thursday, we will use this meeting to review blockers and decide what to do. In the meantime, please keep also an eye on the Fedora 28 Final Blocker list [2]. For more details about this meeting please follow the [3] link. [1] https://apps.fedoraproject.org/calendar/meeting/9025/ [2] http://qa.fedoraproject.org/blockerbugs/milestone/28/final/buglist [3] https://fedoraproject.org/wiki/Go_No_Go_Meeting Thank you in advance for your support. Regards, Jan -- Jan Kuřík JBoss EAP Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

Fedora 28 Final Freeze
by Mohan Boddu 17 Apr '18

17 Apr '18

Hi all, Today, April 17th 2018, is an important day on the Fedora 28 schedule [1], with significant cut-offs. Today we have the Final Freeze [2]. This means that only packages which fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted and packages can move to the 'updates' repository, pending updates will be pushed before final release as zero day updates. [1] https://fedoraproject.org/wiki/Releases/28/Schedule [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/28/final/buglist Regards, Release Engineering

1 0

Renaming "docker" references to generic ones like "container" or "OCI'
by Sushma Gajanur Shivakumar 13 Apr '18

13 Apr '18

Hi All, As the container landscape has changed over the last few years, Docker Inc. has changed what the term "docker" means. Along with changes in the container namespace with tools like buildah, cri-o, rkt and other ways to run containers, it makes sense to refer to containers in a more generic sense, using terms like "container" or "OCI(Open Container Initiative)" instead of "docker". We have already renamed the Docker namespace to "containers" in dist-git. The Bugzilla project for containers is under container as well. Wherever possible to be consistent with using more generic terms, "docker" should be renamed to an appropriate generic term. This will allow us to more seamlessly adapt and change with the continuing evolution of the container based world. A side effect is that the changes will more closely align us with ongoing work within Red Hat. There are several areas that can be evaluated for changes from "docker" to "container" (or OCI). These include: - Changing a package description to be more generic - Working with upstream to rename the project and bringing that back to - Fedora - Changing labels and descriptions used within Dockerfiles The non-exhaustive* full list of current containers[1] and packages[2] to be considered is not a very large list and your consideration and efforts to help are greatly appreciated. ** The bellow URLs will not show a package that is using docker only inthe package description which shows up in bugzilla along with otherlocations[1] https://src.fedoraproject.org/projects/container/%2A <https://src.fedoraproject.org/projects/container/%2A>[2] https://src.fedoraproject.org/projects/*docker* <https://src.fedoraproject.org/projects/*docker*>* Best Regards, Sushma Shivakumar RCM Project Manager Red Hat, Brno

1 0

Migrating jenkins.fedorainfracloud.org to jenkins-fedora-infra.apps.ci.centos.org
by Brian Stinson 12 Apr '18

12 Apr '18

Good Morning Everyone, The Fedora Infrastructure has been running a jenkins instance in its cloud for their own needs. That instance gained some tractions in our community to the point that some projects are relying on it. Unfortunately, our best-effort isn't sufficient to keep this instance in a state that makes it useful for all of its users. The CentOS infrastructure has offered to take over this instance and its maintenance, they have much more expertise than us with jenkins and are already maintaining multiple instances for other needs (including the different CI pipelines now running for Fedora). We want to do this migration in two steps: 1/ migrate all projects from fedorainfracloud.org to ci.centos.org in such a way that there will be no work needed from any of the projects currently using fedorainfracloud (except maybe changing the URLs we do not have access to) 2/ work with the different projects on a case by case basis to help them migrate to the setup that is used more commonly in ci.centos.org with dynamic provisioning of the builder giving the projects full access to them (ie: you will be able to install directly all your dependencies on the builder without having to request the infra team for it) We are now ready for step (1): move over the fedorainfracloud instance to ci.centos.org. All projects set up in fedorainfracloud have been ported to ci.centos.org which has been set up to mirror the instance Fedora was running. So you will find there the same plugin, set up in the same way as in Fedora. Similarly, you will be able to log in the centos instance using your Fedora credentials. Historical job logs were not migrated to the new instance, please open a ticket if previous logs are needed. We have setup redirects to the ci.centos.org instance. We have adjusted the URLs pointing to fedorainfracloud in pagure. You may want to update the URLs we do not have access to and double-check that everything is running as expected for your projects. In case you have any problems, you can reach us on #fedora-admin on IRC or by opening a ticket at https://pagure.io/fedora-infrastructure/ If you'd like to get started on step (2) on your own, the first step is to request a project: https://wiki.centos.org/SIGGuide/SIGProcess/AccountsCI The CentOS CI team will walk you through the rest of the process from there. Thanks for your attention and happy testing! Brian & Pierre - For the CentOS and Fedora Infrastructure Teams

1 0

F28 Self Contained Change: java-openjdk 10 - rolling release for Short Term Support releases of OpenJDK
by Jan Kurik 11 Apr '18

11 Apr '18

This is a late proposal for F28 release, mostly to spread awareness of the availability of java-openjdk 10 in Fedora. It is not closely tied to the F28 release however it would be good to have this in the formal F28 scope. That is the reason, why after a discussion with the Change owner, this is announced as a Self Contained Change Proposal. = Proposed Self Contained Change: java-openjdk 10 - rolling release for Short Term Support releases of OpenJDK = https://fedoraproject.org/wiki/Changes/java-openjdk-10 Owner(s): * Jiri Vanek <jvanek at redhat dot com> OpenJDK have release cadence of 6 months. but 3/4 of them are Short Term Supported for 6 months only. This package is designed to harbore them. Currently it is build on openJDK 10. LTSs (next is 11) will go as separate packages. See announcement: http://mail.openjdk.java.net/pipermail/discuss/2017-September/004281.html<br /> See java SIG plans: https://jvanek.fedorapeople.org/devconf/2018/changesInjavaReleaseProcess.pdf == Detailed description == JDK10 is next major release of Java platform. It is bringing many cool improvements - http://openjdk.java.net/projects/jdk/10/ and is landing to your Fedora. Where it will be maintained for f27 and newer. Unluckily, it is STS (short term support) version. Between individual LTS will be always several STS. Again, please See announcement: http://mail.openjdk.java.net/pipermail/discuss/2017-September/004281.html and See java SIG plans: https://jvanek.fedorapeople.org/devconf/2018/changesInjavaReleaseProcess.pdf . So this is rolling release of all STSs to come. Its fate during the release of fresh LTS is yet to be decided. You will always be allowed to install Used LTS in fedora build root, alongside with latest STS via alternatives. == Scope == * Proposal owners: This is isolated change. The maintainers of OpenJDK in Fedora must build the binaries, and keep them working. Still, to keep this rolling release will be soem packaging challenge. Lets see this when JDK12 (or maybe already 11) come out. * Other developers: Should slowly start to check theirs packages against JDK10 * Release engineering: #7433 - https://pagure.io/releng/issue/7433 * 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

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce April 2018