devel-announce June 2017

devel-announce@lists.fedoraproject.org

9 participants
30 discussions

Guidelines change] Changes to the packaging guidelines
by Jason L Tibbitts III 07 Jun '17

07 Jun '17

Here are the recent changes to the packaging guidelines. ----- The guidelines for enabling services by default modified to indicate that FESCo approval is required for services which change the behavior of other services. * https://fedoraproject.org/wiki/Packaging:DefaultServices#Restrictions * https://pagure.io/packaging-committee/issue/683 ----- A very minor tweak was made to the bootstrapping guidelines to invert the sense of a test so that it matches expectations. * https://fedoraproject.org/wiki/Packaging:Guidelines#Bootstrapping * https://pagure.io/packaging-committee/issue/684 ----- The python guidelines were updated to mention that "python-" MUST NOT be used in dependencies unless the proper "python2-" or "python3-" packages do not exist. * https://fedoraproject.org/wiki/Packaging:Python#Dependencies * https://pagure.io/packaging-committee/issue/686 ----- The naming guidelines have been altered to indicate that python2 binary packages MUST be named starting with "python2-" and that python3 binary package MUST be named starting with "python3-". The section on the old naming conventions for python packages has been removed as it has not been acceptable for many releases now. * https://fedoraproject.org/wiki/Packaging:Naming#Python_modules * https://pagure.io/packaging-committee/issue/685 ----- The guidelines for package dependencies were cleaned up and modified to indicate that all package dependencies MUST be satisfiable within the official Fedora repositories. A statement reiterating that fact was added to the page on weak dependencies as well. * https://fedoraproject.org/wiki/Packaging:Guidelines#Package_Dependencies * https://fedoraproject.org/wiki/Packaging:WeakDependencies * https://pagure.io/packaging-committee/issue/688

1 0

REMINDER: Bugzilla 5 beta feedback
by Christine Freitas 05 Jun '17

05 Jun '17

Hello All, The Bugzilla 5 beta [1] is in full swing! We encourage you to test your current scripts and take part in the beta discussions on the Fedora development list [2]. Partners and customers may also use their existing communications channels to share feedback or questions. We've extended the beta window and ask that you provide feedback or questions by Wednesday, June 14th. The official release date for Bugzilla 5 will be determined based on the beta feedback. We are actively working the action items necessary for release. We will communicate to you as the beta continues to progress. For more information refer to: https://beta-bugzilla.redhat.com/page.cgi?id=whats-new.html https://beta-bugzilla.redhat.com/page.cgi?id=release-notes.html https://beta-bugzilla.redhat.com/page.cgi?id=faq.html https://beta-bugzilla.redhat.com/docs/en/html/using/index.html https://beta-bugzilla.redhat.com/docs/en/html/api/index.html Cheers, the Red Hat Bugzilla team. 1: https://beta-bugzilla.redhat.com/ 2: https://lists.fedoraproject.org/archives/list/devel%40lists. fedoraproject.org/

1 0

Please note that F26 schedule does not affect F27 change deadlines
by Matthew Miller 02 Jun '17

02 Jun '17

I just wanted to call out in particular this bit from Jan's note: > This slip of the F26 release does not have any impact on F27 schedule [3]. > [3] https://fedoraproject.org/wiki/Releases/27/Schedule This means that system-wide changes for Fedora 27 should be submitted to FESCo *before* the Fedora 26 final release. Changes which require a mass rebuild should be in _this_ month. -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 0

Fedora 26 Beta status is NO-GO
by Jan Kurik 02 Jun '17

02 Jun '17

Release status of the Fedora 26 Beta is NO-GO. After 23 hours long Go/No-Go meeting for F26 Beta 1.4 compose [1] we have decided to slip the whole F26 release for one week [2]. The main concern for not releasing this compose [1] as GOLD is unclear resolution of bug #1397087, which is still causing some issues during testing. There is going to be one more Go/No-Go meeting the next Thursday, June 8th, 2017 to verify we are ready for the release. This slip of the F26 release does not have any impact on F27 schedule [3]. For more information please find the logs or minutes from the meeting [4][5]. [1] https://kojipkgs.fedoraproject.org/compose/26/Fedora-26-20170531.0/compose/ [2] https://fedoraproject.org/wiki/Releases/26/Schedule [3] https://fedoraproject.org/wiki/Releases/27/Schedule [4] https://meetbot.fedoraproject.org/fedora-meeting-2/2017-06-01/f26-beta-go-n… [5] https://meetbot.fedoraproject.org/fedora-meeting-2/2017-06-01/f26-beta-go-n… 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

F27 Self Contained Change: Node.js 8.x
by Jan Kurik 01 Jun '17

01 Jun '17

= Proposed Self Contained Change: Node.js 8.x = https://fedoraproject.org/wiki/Changes/NodeJS8x Change owner(s): * Zuzana Svetlikova <zsvetlik AT redhat DOT com> Fedora 27 will be updated to Node.js 8.x, the latest LTS release of the platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. == Detailed Description == Node.js has seen many changes between v6.x and v8.x. Note that this release includes API updates that may require dependency updates. Upstream maintains an exhaustive list of interesting changes here: https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V8.md Node.js 8.x will be under active development until October 2017, at which time it will enter its long-term stable release, which will be maintained actively through April 2019 and for security issues until December 2019. == Scope == Proposal owners: - Update nodejs - Rebuild all binary modules, apply patches as necessary * Other developers: Other Node.js packagers' attention may be required if the update causes issues for their packages. * Release engineering: N/A * Policies and guidelines: No expected changes * 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 June 2017