DevHeads.net

Postings by Stephen Gallagher

Schedule for Friday's FESCo Meeting (2016-05-06)

Following is the list of topics that will be discussed in the FESCo meeting
Friday at 16:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2016-05-06 16:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1444 updates deliverables
.fesco 1444
<a href="https://fedorahosted.org/fesco/ticket/1444" title="https://fedorahosted.org/fesco/ticket/1444">https://fedorahosted.org/fesco/ticket/1444</a>

#topic #1514 Policy for autogenerated code
.fesco 1514
<a href="https://fedorahosted.org/fesco/ticket/1514" title="https://fedorahosted.org/fesco/ticket/1514">https://fedorahosted.org/fesco/ticket/1514</a>

#topic #1570 F24 Changes not in ON_QA st

RE: Plans for Node.js 6.x

Sent from my Galaxy Tab® S2-------- Original message --------From: drago01 < ... at gmail dot com> Date: 5/1/2016 12:00 PM (GMT-05:00) To: Development discussions related to Fedora < ... at lists dot fedoraproject.org> Subject: Re: Plans for Node.js 6.x
On Wed, Apr 27, 2016 at 4:00 AM, Stephen Gallagher < ... at redhat dot com> wrote:

Node.js downgraded to 4.x LTS in Fedora 24

As previously discussed on the fedora-devel list, the Node.js SIG has elected to
downgrade Node.js to the 4.x long-term-support branch rather than ship with the
5.x new-feature branch due to its support lifecycle ending this summer.

I have just bumped epoch and built the new 4.x package in Fedora 24 (along with
several archful modules that required a rebuild to work with the older version).
If you rely on Node.js (even just as part of your builddeps, such as with
nodejs-less), please test and give karma on
<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2016-2d314bc898" title="https://bodhi.fedoraproject.org/updates/FEDORA-2016-2d314bc898">https://bodhi.fedoraproject.org/updates/FEDORA-2016-2d314bc898</a>

Plans for Node.js 6.x

OK folks, it's Bad Decision Time.

Today, Node.js 6.0 was released. This is a significant ABI-breaking release,
which means there is no guarantee that existing modules will work with it at all.[1]

Better still, Node.js 5.x is only going to be supported until sometime this
summer, because they're aiming for the 6.x branch to become the new LTS in
October[2].

Node.js 5.9.0 coming to Rawhide next week

Next week, I plan to upgrade Node.js from the 4.x LTS branch to the 5.x stable
branch in Rawhide. This upgrade does break backwards-compatibility and thus will
need re-testing of modules. Also, all native NPMs (those that are built with
architecture-specific packages rather than noarch) will need to be rebuilt to
pick up the new automatic dependency system we have implemented.

Previously, native modules had to be rebuilt for every minor-version bump of
Node.js, but we have tweaked the virtual Provides and Requires to only require a
rebuild at major-version bumps.

Best practices for splitting off a directory to a new partition

During a recent Fedora Server SIG meeting where we were discussing the default
filesystem layout (if you just let Anaconda automatically create partitions),
there was a lot of talk about how certain directories such as /var/log or
/var/www/html, etc. are often split off into their own partitions at customer
sites.

LUA expert to help convert fedora-release %post scripts

As part of efforts in Fedora 24 to address certain issues with the
edition-specific fedora-release content (such as /etc/os-release, /etc/issues
and edition-specific presets), I built a moderately complex series of bash
scripts to run in %post and %posttrans to ensure that all of the right files
were symlinked in the correct places.

Unfortunately, the result here is that %post and %posttrans for fedora-release
now requires both bash and coreutils to function properly, and this introduces a
cyclical dependency.

Orphaning python-django-haystack and python-django-pipeline in Fedora

I no longer need these packages in Fedora (they were there to support Review
Board which is now only in EPEL due to Django incompatibilities), so I've
orphaned them.

I will continue to maintain them on EPEL 7.

Schedule for Friday's FESCo Meeting (2016-02-12)

Following is the list of topics that will be discussed in the FESCo
meeting Friday at 17:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2016-02-12 17:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1539 Are 32-bit upgrades to Fedora 24 release blocking?

Schedule for Friday's FESCo Meeting (2016-02-05)

Following is the list of topics that will be discussed in the FESCo
meeting Friday at 17:00UTC in #fedora-meeting on irc.freenode.net.

NOTE: due to DevConf.cz, we may not have quorum and these may be discussed
next week instead.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2016-02-05 17:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1539 Are 32-bit upgrades to Fedora 24 release blocking?

Fedora Policy on generated code

Please keep responses on the devel@ list. CCed to the Council list for
visibility and discussion of how this fits with our "Freedom" foundation.

== Premise ==
Some upstream distribute tarballs that include code and content that
has been generated at distribution time.

Schedule for Wednesday's FESCo Meeting (2015-12-09)

Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2015-12-09 18:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1444 updates deliverables
.fesco 1444
<a href="https://fedorahosted.org/fesco/ticket/1444" title="https://fedorahosted.org/fesco/ticket/1444">https://fedorahosted.org/fesco/ticket/1444</a>

#topic #1478 F24 Self Contained Changes
.fesco 1478
<a href="https://fedorahosted.org/fesco/ticket/1478" title="https://fedorahosted.org/fesco/ticket/1478">https://fedorahosted.org/fesco/ticket/1478</a>

= New business =

#topic #1511 F24 Syste

Some analysis on the size of the minimal and Server installs of Fedora 23

(Please keep responses on the devel@ list; I've set it in the Reply-To.)

To jump right to the premise: The default Fedora Server install is Way
Too Big(TM) and the minimal install (also available on the Fedora
Server install media) is also Too Big.

I've been trying to do some quick-and-dirty analysis of what is in
these default installations in order to figure out where we should be
focusing our efforts. I'll point out that there are two goals that we
need to keep in mind (and the reasons behind them) in order of
increasing importance:

1) Reduce disk space usage.

Seeking help to maintain Review Board packages for Fedora and RHEL/CentOS

As time goes on, it has become more and more difficult to dedicate the
time to maintain the RPM packages of Review Board on Fedora and EPEL.
My day-job responsibilities have increased and I can't spare as much
time as I used to for personal projects like this one.

I still use Review Board daily and will continue to maintain it as
time permits, but I'm looking for someone (ideally with packaging
experience) to assist me, particularly when security releases come out
and I'm unavailable.

System V to systemd unit migration

At the FESCo meeting on October 14th, it was ​decided that the time
has come to finally complete the migration away from System V init
scripts. What does this mean for you as a packager?

When we branch from Rawhide for Fedora 24 (currently ​scheduled for
February 2nd, 2016), we will be immediately retiring any package in
the Fedora collection that relies on a System V init script instead of
a systemd unit file to start.

Schedule for Wednesday's FESCo Meeting (2015-10-07)

Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2015-10-07 18:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1483 Decision on bundling policy in the Fedora Package Collectio
n
.fesco 1483
<a href="https://fedorahosted.org/fesco/ticket/1483" title="https://fedorahosted.org/fesco/ticket/1483">https://fedorahosted.org/fesco/ticket/1483</a>

= New business =

#topic #1484 unresponsive maintainer: chitlesh
.fesco 1484
<a href="https://fedorahost" title="https://fedorahost">https://fedorahost</a>

Proposal to reduce anti-bundling requirements

I assume that subject line got your attention.

I know this is a long-standing debate and that this thread is likely
to turn into an incomprehensible flamewar filled with the same tired
arguments, but I'm going to make a proposal and then attempt to
respond to many of those known arguments up-front (in the hopes that
we can try to keep the conversation on-track). Please keep the
conversation on <a href="mailto: ... at lists dot fedoraproject.org"> ... at lists dot fedoraproject.org</a> . I CCed packaging@ to
make them aware of this discussion.

Right now, we have a policy that essentially forbids source code from
being bundled into a package.

Schedule for Wednesday's FESCo Meeting (2015-08-19)

Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2015-08-19 18:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1466 non-responsive maintainer exception process for skottler
.fesco 1466
<a href="https://fedorahosted.org/fesco/ticket/1466" title="https://fedorahosted.org/fesco/ticket/1466">https://fedorahosted.org/fesco/ticket/1466</a>

= New business =

#topic #1471 F24 System Wide Change: TeXLive 2015
.fesco 1471
<a href="https://fedorahoste" title="https://fedorahoste">https://fedorahoste</a>

Schedule for Wednesday's FESCo Meeting (2015-07-22)

Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2015-07-22 18:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1462 RPM Weak Dependencies and the install media compose
process
.fesco 1462
<a href="https://fedorahosted.org/fesco/ticket/1462" title="https://fedorahosted.org/fesco/ticket/1462">https://fedorahosted.org/fesco/ticket/1462</a>

= New business =

#topic #1463 upgrades for F23 and beyond
.fesco 1463
<a href="https://fedorahosted.org/" title="https://fedorahosted.org/">https://fedorahosted.org/</a>

RPM Weak Dependencies and the install media compose process

(Please keep the conversation on the devel list; I'm CCing it the rel
-eng list to make sure all the relevant people see the initial message)

This past week, the Fedora Packaging Committee approved the use of
"weak dependencies" in Fedora.

Fedora.next PRD refresh

== Overview ==

Back at the beginning of the Fedora.next initiative when we created the
working groups, we tasked them with creating "Product Requirement
Documents" (PRDs) to guide the development of each of these core
groups.
* <a href="https://fedoraproject.org/wiki/Workstation/Workstation_PRD" title="https://fedoraproject.org/wiki/Workstation/Workstation_PRD">https://fedoraproject.org/wiki/Workstation/Workstation_PRD</a>
*
<a href="https://fedoraproject.org/wiki/Env_and_Stacks/Product_Requirements_Doc" title="https://fedoraproject.org/wiki/Env_and_Stacks/Product_Requirements_Doc">https://fedoraproject.org/wiki/Env_and_Stacks/Product_Requirements_Doc</a>
ument
* <a href="https://fedoraproject.org/wiki/Cloud/Cloud_PRD?rd=Cloud_PRD" title="https://fedoraproject.org/wiki/Cloud/Cloud_PRD?rd=Cloud_PRD">https://fedoraproject.org/wiki/Cloud/Cloud_PRD?rd=Cloud_PRD</a>
* <a href="https://fedoraproject.org/wiki/Server/Product_Requirements_Document" title="https://fedoraproject.org/wiki/Server/Product_Requirements_Document">https://fedoraproject.org/wiki/Server/Product_Requirements_Document</a>

More than a year has passed and the Fedora Council feels that it's a
good time to give anot

Schedule for Wednesday's FESCo Meeting (2015-02-25)

Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2015-02-25 18:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1367 Please define package manager expectations
.fesco 1367
<a href="https://fedorahosted.org/fesco/ticket/1367" title="https://fedorahosted.org/fesco/ticket/1367">https://fedorahosted.org/fesco/ticket/1367</a>

#topic #1388 Remove echoping from the distribution
.fesco 1388
<a href="https://fedorahosted.org/fesco/ticket/1388" title="https://fedorahosted.org/fesco/ticket/1388">https://fedorahosted.org/fesco/ticket/1388</a>

#topi

Ring-based Packaging Policies

(Logistical note: please keep all replies to this thread on
<a href="mailto: ... at lists dot fedoraproject.org"> ... at lists dot fedoraproject.org</a>)

tl;dr Shall we consider requiring a lesser package review for packages
that are not present on Product or Spin install media?

== Premise ==

So, some time ago, we started talking about dividing up the Fedora
package set into a series of "rings". One of the driving purposes behind
this idea was to re-evaluate our policies for packaging in each of these
rings.

Plan of Record for Fedora 22 Network Install Media

(Cross-posted to the WG mailing lists; please reply only to devel@)

== Overview ==

Today in #anaconda, we had a discussion of the plans for network install
media for Fedora 22. We acknowledged that the network install (and more
generally, unattended installation) story in Fedora 21 was somewhat
lacking.

Schedule for Wednesday's FESCo Meeting (2015-01-07)

Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2015-01-07 18:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1372 "Workstation" Product defaults to wide-open firewall
<a href="https://fedorahosted.org/fesco/ticket/1372" title="https://fedorahosted.org/fesco/ticket/1372">https://fedorahosted.org/fesco/ticket/1372</a>

#topic #1349 Fedora 22 scheduling strategy (and beyond)
<a href="https://fedorahosted.org/fesco/ticket/1349" title="https://fedorahosted.org/fesco/ticket/1349">https://fedorahosted.org/fesco/ticket/1349</a>

#topic #1198 Po

Open Seat on the Fedora Server Working Group

This past week, David Strauss chose to step down from his position on
the Fedora Server Working Group, citing a lack of alignment with his
current work usage. The Fedora Server SIG would like to thank David for
his contributions up to this point and wish him well.

This means that there is currently a vacancy in the Fedora Server
Working Group. The Working Group is the nine-person volunteer body that
oversees the development, testing, release, documentation, marketing and
evangelism of the Fedora Server.

Fedora 21 Final Freeze is tomorrow

As the $SUBJECT says, tomorrow we go into the two-week Final Freeze for
Fedora 21. That means that you need to have all of the packages that you
want to see land in Fedora 21 submitted for stable by the end of the day
*today*. After that point, we will initiate the Final Freeze Policy,
where you will need to request a Freeze Exception (or be fixing a
Blocker bug) in order to get changes into the Final release. Anything
else will be deferred to the [updates] repo for release day.

Fedora 21 Schedule Change

== tl;dr Version ==

We are accelerating the Fedora 21 schedule so that we will enter Final
Freeze one week earlier than previously described on the schedule
page[1]. This means that all fixes intended for inclusion in the Fedora
21 release must be submitted for the stable repository no later than
November 17th (so that we have time to do the updates push and build the
Release Candidate on November 18th). The Final Release date will remain
at December 9th.

Suggested Freeze Policy change for Fedora 22+

I talked to several people over the last couple days about what we can
do to try to avoid the "hero testing" treadmill that we've been on
during every Freeze in recent memory (specifically that we're usually
fixing Blocker bugs until the day before the Go/No-Go meeting and that
means that our QA team is pulling all-night test runs basically every
week).

I made the following suggestion to both Adam Williamson and David
Cantrell over the last couple of days and both seemed to think that this
is a reasonable approach (but for different reasons, interestingly).

Beginning with Alpha Freeze in Fed

Summary/Minutes from today's FESCo Meeting (2014-10-29)

===================================
#fedora-meeting: FESCO (2014-10-29)
===================================

Meeting started by sgallagh at 17:01:02 UTC.