devel-announce November 2016

devel-announce@lists.fedoraproject.org

5 participants
21 discussions

F26 Self Contained Change: Zend Framework 3
by Jan Kurik 30 Nov '16

30 Nov '16

= Proposed Self Contained Change: Zend Framework 3 = https://fedoraproject.org/wiki/Changes/ZF3 Change owner(s): * Remi Collet <remi at fedoraproject dot org> Update Zend Framework to latest version 3. Fedora 24 provides Zend Framework 2.5 (Fedora 25 provides ZF 2.5.3), which is a transition version. == Detailed Description == See upstream annoucement: Zend Framework 3 Released! [https://framework.zend.com/blog/2016-06-28-zend-framework-3.html] The Zend Framework is a huge set of ~60 components. The framework version defines a minimal set of components, and their minimal version. Version 3 is recommend for PHP 7.0 which is also part of Fedora 25. == Scope == * Proposal owners: Update packages and create new for additional components * Other developers: Test their applications * Release engineering: N/A (not a System Wide Change) * 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

Planned Outage: Cloud Environment - 2016-12-01 21:00 UTC
by Stephen John Smoogen 28 Nov '16

28 Nov '16

There will be an outage starting at 2016-12-01 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-12-01 21:00 UTC' Reason for outage: We have been in a freeze for the release of Fedora 25 and have multiple updates across the systems needed to occur. Part of these are to bring RHEL-7 systems to 7.3 and others are to bring some systems to Fedora 25. Affected Services: Cloud Environment - *.fedorainfracloud.org Unaffected Services: Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ Package Database - https://admin.fedoraproject.org/pkgdb/ BFO - https://boot.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - https://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora Insight - https://insight.fedoraproject.org/ Fedora People - https://fedorapeople.org/ Main Website - https://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ QA Services Secondary Architectures Spins - https://spins.fedoraproject.org/ Start - https://start.fedoraproject.org/ Torrent - https://torrent.fedoraproject.org/ Translation Services - https://translate.fedoraproject.org/ Wiki - https://fedoraproject.org/wiki/ Staging - .stg.fedoraproject.org, .stg.phx2.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/5581 Contact Information: infrastructure @lists.fedoraproject.org Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen.

1 0

Planned Outage: General Services Environment - 2016-11-30 21:00 UTC
by Stephen John Smoogen 28 Nov '16

28 Nov '16

There will be an outage starting at 2016-11-30 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-11-30 21:00 UTC' Reason for outage: We have been in a freeze for the release of Fedora 25 and have multiple updates across the systems needed to occur. Part of these are to bring RHEL-7 systems to 7.3 and others are to bring some systems to Fedora 25. Affected Services: Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ Package Database - https://admin.fedoraproject.org/pkgdb/ BFO - https://boot.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - https://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora Insight - https://insight.fedoraproject.org/ Fedora People - https://fedorapeople.org/ Main Website - https://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ QA Services Secondary Architectures Spins - https://spins.fedoraproject.org/ Start - https://start.fedoraproject.org/ Torrent - https://torrent.fedoraproject.org/ Translation Services - https://translate.fedoraproject.org/ Wiki - https://fedoraproject.org/wiki/ Unaffected Services: Staging - .stg.fedoraproject.org, .stg.phx2.fedoraproject.org Ticket Link: TBA Contact Information: infrastructure @lists.fedoraproject.org Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen.

1 0

Planned Outage: 2016-11-29 21:00 UTC Build Environment
by Stephen John Smoogen 28 Nov '16

28 Nov '16

There will be an outage starting at 2016-11-29 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-11-29 21:00 UTC' Reason for outage: We have been in a freeze for the release of Fedora 25 and have multiple updates across the systems needed to occur. Part of these are to bring RHEL-7 systems to 7.3 and others are to bring some systems to Fedora 25. Affected Services: Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ Package Database - https://admin.fedoraproject.org/pkgdb/ Unaffected Services: BFO - https://boot.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - https://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora Insight - https://insight.fedoraproject.org/ Fedora People - https://fedorapeople.org/ Main Website - https://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ QA Services Secondary Architectures Spins - https://spins.fedoraproject.org/ Start - https://start.fedoraproject.org/ Torrent - https://torrent.fedoraproject.org/ Translation Services - https://translate.fedoraproject.org/ Wiki - https://fedoraproject.org/wiki/ Staging - .stg.fedoraproject.org, .stg.phx2.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/5579 Contact Information: infrastructure @lists.fedoraproject.org Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen.

1 0

Planned Outage: Staging Environment - 2016-11-28 21:00 UTC
by Stephen John Smoogen 28 Nov '16

28 Nov '16

There will be an outage starting at 2016-11-28 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-11-28 21:00 UTC' Reason for outage: We have been in a freeze for the release of Fedora 25 and have multiple updates across the systems needed to occur. Part of these are to bring RHEL-7 systems to 7.3 and others are to bring some systems to Fedora 25. Affected Services: Staging - .stg.fedoraproject.org, .stg.phx2.fedoraproject.org Unaffected Services: BFO - https://boot.fedoraproject.org/ Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - https://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora Insight - https://insight.fedoraproject.org/ Fedora People - https://fedorapeople.org/ Main Website - https://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Package Database - https://admin.fedoraproject.org/pkgdb/ QA Services Secondary Architectures Spins - https://spins.fedoraproject.org/ Start - https://start.fedoraproject.org/ Torrent - https://torrent.fedoraproject.org/ Translation Services - https://translate.fedoraproject.org/ Wiki - https://fedoraproject.org/wiki/ Ticket Link: TBA Contact Information: infrastructure @lists.fedoraproject.org Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen.

1 0

Reminder: Fedora 23 End Of Life on 2016-Dec-20
by Jan Kurik 28 Nov '16

28 Nov '16

Fedora 23 support is going to be EOL on Tuesday, December 20th, 2016. At this day we are going to close all the Fedora 23 bugs which will remain open [1]. You have last few weeks to submit your updates to the Fedora 23, if you have any, before the Fedora 23 release becomes unsupported. [1] https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedor… Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

F26 Self Contained Change: Java/OpenJDK enforces the system-wide crypto policy
by Jan Kurik 21 Nov '16

21 Nov '16

= Proposed Self Contained Change:Java/OpenJDK enforces the system-wide crypto policy = https://fedoraproject.org/wiki/Changes/JavaCryptoPolicies Change owner(s): * Nikos Mavrogiannopoulos <nmav AT redhat DOT com> 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. == Detailed Description == 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. After that change the administrator should be assured that any Java application will follow a policy that adheres to the configured profile. == Scope == * Proposal owners: The change requires modifying OpenJDK to read additional security properties from the generated by the crypto policies file (/etc/crypto-policies/back-ends/java.config). * Other developers: There are no required actions by other developers. The change requires only targeted changes to openjdk and crypto-policies. * Release engineering: No actions required. * Policies and guidelines: The packaging guidelines for crypto policies need to be modified to include OpenJDK/java in the list of libraries supporting the policies. * 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

upcoming build and release developer flag day December 12 2016
by Dennis Gilmore 19 Nov '16

19 Nov '16

Hi All, We are wanting to write to you all about an important date coming up. On the 12th of December 2016 we will be making some important changes that will require changes on every developers machine. In this case developers means every one that interacts with koji using authentication lookaside cache checksum hash. currently packages are stored in lookaside cache using md5sum we will be switching to sha256sum. The support for this has been in fedpkg for awhile, we have not switched the default as once we do any source uploaded with sha256sum will only be able to be verified by a client that supports sha256sum. koji authentication will be switching to Kerberos. Koji supports multiple authentication mechanisms. Fedora infrastructure has set up a freeipa instance internally that has credential syncing to fas. We are working on ensuring that gssapi caching is supported so that you can have multiple TGT's and the ability to work in multiple reams at once. you can get started today by doing kinit <fas username>@FEDORAPROJECT.ORG if you move your ~/.fedora.cert file out of the way authentication will still work. Using well known certs for koji.fedoraproject.org arm.koji.fedoraproject.org ppc.koji.fedoraproject.org s390.koji.fedoraproject.org pkgs.fedoraproject.org this is the last step needed to have fedoraproject.org switch to hsts and default to https:// when connecting to any fedora service. It will also remove a lot of questions that new people have when connecting to koji via https. Disable ssl cert authentication in koji. With the switch to keberos and the change of ssl certificates on the koji and pkgs servers we will be disabling the ability to login to koji using a ssl certificate completely. This change will require new koji client configurations for everyone. Gate rawhide builds. Gating will enable us to sign rawhide builds and switch the rawhide repo to having gpgcheck enabled. In order to achieve everything we have to break end user configurations. All users will need to have new enough versions of fedora-packager, fedpkg, rpkg, koji. the exact versions needed are not yet known as some enhancements are still being worked on. We will be aiming to have everything pushed stable right before the flag day. Some of the changes will not be compatible with the existing setup. We anticipate keeping everyone informed as we move forward about any actions that will need to be taken on the developer side. there is a wiki page at https://fedoraproject.org/wiki/ReleaseEngineering/FlagDay2016 that will be updated as more is known. Not in scope at this point is using kerberos for ssh or other apps supported by infrastructure, though it is not ruled out going forward. If you have any questions please respond here or in #fedora-releng on freenode Thanks Release Engineering and Infrastructure

1 0

Fedora 25 Final compose 1.3 is considered as GOLD and the status is GO
by Jan Kurik 17 Nov '16

17 Nov '16

At the second round of Fedora 25 Final Go/No-Go Meeting, has just been Fedora 25 Final compose 1.3 declared as GOLD. GA of this release is planed on Tuesday 2016-November-22. Meeting details can be seen here: Log: https://meetbot.fedoraproject.org/fedora-meeting-2/2016-11-17/f25-final-gon… Minutes: https://meetbot.fedoraproject.org/fedora-meeting-2/2016-11-17/f25-final-gon… Thanks everyone who participated on this release! Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

F26 System Wide Change: Fedora 26 Boost 1.63 upgrade
by Jan Kurik 17 Nov '16

17 Nov '16

= System Wide Change: Fedora 26 Boost 1.63 upgrade = https://fedoraproject.org/wiki/Changes/F26Boost163 Change owner(s): * Jonathan Wakely < jwakely AT redhat DOT com > This change brings Boost 1.63.0 to Fedora 26. This will mean F26 ships with a recent upstream Boost release. == Detailed Description == The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is one of explicit Boost non-goals, this entails rebuilding of all dependent packages. This has also always entailed yours truly assisting maintainers of client packages in decoding cryptic boost-ese seen in output from g++. Such care is to be expected this time around as well. Boost 1.63 is scheduled for release on Dec 14th, 2016. It's possible that 1.64.0 will be released early enough in the F26 schedule to rebase on that instead, with beta releases available for testing in advance. == Scope == * Proposal owners: - Build will be done with Boost.Build v2 (which is the upstream-sanctioned way of building Boost) - Request a "f25-boost" build system tag (discussion): https://fedorahosted.org/rel-eng/ticket/6235 → f24-boost - Build boost into that tag (take a look at the build #606493 for inspiration) - Post a request for rebuilds to fedora-devel - Work on rebuilding dependent packages in the tag. - When most is done, re-tag all the packages to rawhide - Watch fedora-devel and assist in rebuilding broken Boost clients (by fixing the client, or Boost). * Other developers: Those who depend on Boost DSOs will have to rebuild their packages. Feature owners will alleviate some of this work as indicated above, and will assist those whose packages fail to build in debugging them. * Release engineering: Side tag creation. * List of deliverables: All deliverables will include updated Boost packages * Policies and guidelines: Apart from scope, this is business as usual, so no policies, no guidelines. * 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce November 2016