DevHeads.net

Postings by Jan Kurik

Reminder meeting : Modularity WG (once every two weeks)

Dear all,

You are kindly invited to the meeting:
Modularity WG (once every two weeks) on 2017-05-30 from 10:00:00 to 11:00:00 US/Eastern
At <a href="mailto:fedora-meeting- ... at irc dot freenode.net">fedora-meeting- ... at irc dot freenode.net</a>

The meeting will be about:
Meeting of the Modularity Working Group.

More information available at: [Modularity Working Group wiki page](<a href="https://fedoraproject.org/wiki/Modularity_Working_Group" title="https://fedoraproject.org/wiki/Modularity_Working_Group">https://fedoraproject.org/wiki/Modularity_Working_Group</a>)

The agenda for the meeting is available at [modularity-wg-agendas pad](<a href="https://board.net/p/modularity-wg-agendas" title="https://board.net/p/modularity-wg-agendas">https://board.net/p/modularity-wg-agendas</a>).

Source: <a href="https://apps.fedoraproject.org/calendar/meeting/5249/" title="https://apps.fedoraproject.org/calendar/meeting/5249/">https://apps.fedoraproject.org/calendar/meeting/5249/</a>

F27 System Wide Change: Rsyslog log format change proposal

= Proposed System Wide Change: Rsyslog log format change proposal =
<a href="https://fedoraproject.org/wiki/Changes/RsyslogLogFormat" title="https://fedoraproject.org/wiki/Changes/RsyslogLogFormat">https://fedoraproject.org/wiki/Changes/RsyslogLogFormat</a>

Change owner(s):
* Radovan Sroka <rsroka AT redhat DOT com>
* Roman Pavelka <rpavelka AT redhat DOT com>

Currently Fedora uses RSYSLOG_TraditionalFileFormat as a default
format for timestamps in its logs.

Fedora 26 Beta status is NO-GO

Release status of the Fedora 26 Beta is NO-GO.

Due to missing RC of Fedora 26 Beta release and presence of blocker
bugs [1] we are delaying release of Fedora 26 Beta for one week.
There is going to be one more Go/No-Go meeting the next Thursday, June
1st, 2017 at 17:00 UTC to verify we are ready for the release.

For more information please find the logs or minutes from the meeting [2][3].

[1] <a href="https://qa.fedoraproject.org/blockerbugs/milestone/26/beta/buglist" title="https://qa.fedoraproject.org/blockerbugs/milestone/26/beta/buglist">https://qa.fedoraproject.org/blockerbugs/milestone/26/beta/buglist</a>
[2] <a href="https://meetbot.fedoraproject.org/fedora-meeting-2/2017-05-25/f26-beta-go-no-go-meeting.2017-05-25-17.00.html" title="https://meetbot.fedoraproject.org/fedora-meeting-2/2017-05-25/f26-beta-go-no-go-meeting.2017-05-25-17.00.html">https://meetbot.fedoraproject.org/fedora-meeting-2/2017-05-25/f26-beta-g...</a>
[3] <a href="https://meetbot" title="https://meetbot">https://meetbot</a>.

F27 System Wide Change: Ruby on Rails 5.1

= Proposed System Wide Change:Ruby on Rails 5.1 =
<a href="https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_5.1" title="https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_5.1">https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_5.1</a>

Change owner(s):
* Pavel Valena <pvalena AT redhat DOT com>
* Vít Ondruch <vondruch AT redhat DOT com>
* Jun Aruga <jaruga AT redhat DOT com>

Ruby on Rails 5.1 is the latest version of well known web framework
written in Ruby.

== Detailed Description ==
The Ruby on Rails stack is evolving quickly and Fedora needs to keep
pace with it.

Reminder meeting : Fedora 26 Beta Release Readiness Meeting

Dear all,

You are kindly invited to the meeting:
Fedora 26 Beta Release Readiness Meeting on 2017-05-25 from 19:00:00 to 21:00:00 UTC
At <a href="mailto:fedora-meeting- ... at irc dot freenode.net">fedora-meeting- ... at irc dot freenode.net</a>

The meeting will be about:
We will meet to make sure we are coordinated and ready for the Beta
release of Fedora 26.

Reminder meeting : Fedora 26 Beta Go/No-Go Meeting

Dear all,

You are kindly invited to the meeting:
Fedora 26 Beta Go/No-Go Meeting on 2017-05-25 from 17:00:00 to 19:00:00 UTC
At <a href="mailto:fedora-meeting- ... at irc dot freenode.net">fedora-meeting- ... at irc dot freenode.net</a>

The meeting will be about:
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.

Fedora 26 Beta Release Readiness Meeting on Thursday, May 25 @ 19:00 UTC

Join us on irc.freenode.net in #fedora-meeting-2 for the Fedora 26
Beta Release Readiness Meeting meeting.

The meeting is going to be held on Thursday, May 25, 2017 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 Beta
release of Fedora 26.

Fedora 26 Beta Go/No-Go Meeting on Thursday, May 25 @ 17:00 UTC

Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 26
Beta.

The meeting is going to be held on Thursday, May 25, 2017 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.

Reminder meeting : Modularity WG (once every two weeks)

Dear all,

You are kindly invited to the meeting:
Modularity WG (once every two weeks) on 2017-05-16 from 10:00:00 to 11:00:00 US/Eastern
At <a href="mailto:fedora-meeting- ... at irc dot freenode.net">fedora-meeting- ... at irc dot freenode.net</a>

The meeting will be about:
Meeting of the Modularity Working Group.

More information available at: [Modularity Working Group wiki page](<a href="https://fedoraproject.org/wiki/Modularity_Working_Group" title="https://fedoraproject.org/wiki/Modularity_Working_Group">https://fedoraproject.org/wiki/Modularity_Working_Group</a>)

The agenda for the meeting is available at [modularity-wg-agendas pad](<a href="https://board.net/p/modularity-wg-agendas" title="https://board.net/p/modularity-wg-agendas">https://board.net/p/modularity-wg-agendas</a>).

Source: <a href="https://apps.fedoraproject.org/calendar/meeting/5249/" title="https://apps.fedoraproject.org/calendar/meeting/5249/">https://apps.fedoraproject.org/calendar/meeting/5249/</a>

F27 System Wide Change: Perl 5.26

= Proposed System Wide Change: Perl 5.26 =
<a href="https://fedoraproject.org/wiki/Changes/perl5.26" title="https://fedoraproject.org/wiki/Changes/perl5.26">https://fedoraproject.org/wiki/Changes/perl5.26</a>

Change owner(s):
* Jitka Plesníková <jplesnik AT redhat DOT com>
* Petr Písař <ppisar AT redhat DOT com>

A new perl 5.26 version brings a lot of changes done over a year of
development. Perl 5.26 will be released 5/20/2017. See 5.26.0-RC
perldelta for more details about preparing release.
<a href="http://search.cpan.org/dist/perl-5.26.0-RC1/pod/perldelta.pod" title="http://search.cpan.org/dist/perl-5.26.0-RC1/pod/perldelta.pod">http://search.cpan.org/dist/perl-5.26.0-RC1/pod/perldelta.pod</a>

== Detailed Description ==
New perl is released every year and updates containing mainly bug
fixes follow during the year.

REMINDER: Fedora 26 Change Checkpoint: 100% Code Complete Deadline & Beta Freeze in 1 week

The next Tuesday, on 2017-May-16, we will reach two important
milestones of the Fedora 26 release [1]:

== Change Checkpoint: 100% Code Complete Deadline [2] ==
* New accepted changes must be code complete, meaning all the code
required to enable to the new change is finished.
* The level of code completeness is reflected as tracker bug state
ON_QA. The change does not have to be fully tested by this deadline.

== Beta Freeze [3] ==
Only packages which fix accepted blocker or freeze exception bugs [4]
will be marked as 'stable' and included in the Beta composes.

F27 System Wide Change: Arbitrary Branching

= Proposed System Wide Change: Arbitrary Branching =
<a href="https://fedoraproject.org/wiki/Changes/ArbitraryBranching" title="https://fedoraproject.org/wiki/Changes/ArbitraryBranching">https://fedoraproject.org/wiki/Changes/ArbitraryBranching</a>

Change owner(s):
* Matt Prahl <mprahl AT redhat DOT com>

Tooling changes to support the new way of branching for Fedora 27.

== Detailed Description ==
To avoid maintaining multiple copies of this information, please read
the Arbitrary Branching Focus Document (updated May 3rd, 2017) in the
Factory2 space as a substitute for this document:
<a href="https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/ArbitraryBranching" title="https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/ArbitraryBranching">https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/ArbitraryBr...</a>

For further information, view this section of Ralph Bean’s
pres

Reminder meeting : Modularity WG (once every two weeks)

Dear all,

You are kindly invited to the meeting:
Modularity WG (once every two weeks) on 2017-05-02 from 10:00:00 to 11:00:00 US/Eastern
At <a href="mailto:fedora-meeting- ... at irc dot freenode.net">fedora-meeting- ... at irc dot freenode.net</a>

The meeting will be about:
Meeting of the Modularity Working Group.

More information available at: [Modularity Working Group wiki page](<a href="https://fedoraproject.org/wiki/Modularity_Working_Group" title="https://fedoraproject.org/wiki/Modularity_Working_Group">https://fedoraproject.org/wiki/Modularity_Working_Group</a>)

The agenda for the meeting is available at [modularity-wg-agendas pad](<a href="https://board.net/p/modularity-wg-agendas" title="https://board.net/p/modularity-wg-agendas">https://board.net/p/modularity-wg-agendas</a>).

Source: <a href="https://apps.fedoraproject.org/calendar/meeting/5249/" title="https://apps.fedoraproject.org/calendar/meeting/5249/">https://apps.fedoraproject.org/calendar/meeting/5249/</a>

F27 Self Contained Change: Java 9

= Proposed Self Contained Change: Java 9 =
<a href="https://fedoraproject.org/wiki/Changes/Java9TechPreview" title="https://fedoraproject.org/wiki/Changes/Java9TechPreview">https://fedoraproject.org/wiki/Changes/Java9TechPreview</a>

Change owner(s):
* Jiri Vanek <jvanek at redhat dot com>

Add a tech preview preview of the the upcoming version of Java
(OpenJDK9) to Fedora 27

== Detailed Description ==
The current Java implementation in Fedora comes from OpenJDK.
Java 9 (and OpenJDK9) are tentatively scheduled for release in
2017-07-27. Fedora 27 will most likely be out just a few months after
that, and is therefore positioned to receive a tech preview version of
the latest OpenJDK9 candidates.

Reminder meeting : Modularity WG (once every two weeks)

Dear all,

You are kindly invited to the meeting:
Modularity WG (once every two weeks) on 2017-04-18 from 10:00:00 to 11:00:00 US/Eastern
At <a href="mailto:fedora-meeting- ... at irc dot freenode.net">fedora-meeting- ... at irc dot freenode.net</a>

The meeting will be about:
Meeting of the Modularity Working Group.

More information available at: [Modularity Working Group wiki page](<a href="https://fedoraproject.org/wiki/Modularity_Working_Group" title="https://fedoraproject.org/wiki/Modularity_Working_Group">https://fedoraproject.org/wiki/Modularity_Working_Group</a>)

The agenda for the meeting is available at [modularity-wg-agendas pad](<a href="https://board.net/p/modularity-wg-agendas" title="https://board.net/p/modularity-wg-agendas">https://board.net/p/modularity-wg-agendas</a>).

Source: <a href="https://apps.fedoraproject.org/calendar/meeting/5249/" title="https://apps.fedoraproject.org/calendar/meeting/5249/">https://apps.fedoraproject.org/calendar/meeting/5249/</a>

F27 System Wide Change: Switch libcurl back to OpenSSL

= Proposed System Wide Change: Switch libcurl back to OpenSSL =
<a href="https://fedoraproject.org/wiki/Changes/libcurlBackToOpenSSL" title="https://fedoraproject.org/wiki/Changes/libcurlBackToOpenSSL">https://fedoraproject.org/wiki/Changes/libcurlBackToOpenSSL</a>

Change owner(s):
* Kamil Dudka <kdudka AT redhat DOT com>

libcurl in Fedora currently uses the NSS (Network Security Services)
library for TLS and cryptography. After implementing this change,
libcurl will use OpenSSL instead of NSS.

== Detailed Description ==
In order to make even smaller Fedora base images, it was proposed to
switch libcurl back to OpenSSL.

F27 System Wide Change: Switch libidn-using applications to IDNA2008

= Proposed System Wide Change: Switch libidn-using applications to IDNA2008 =
<a href="https://fedoraproject.org/wiki/Changes/IDNA2008" title="https://fedoraproject.org/wiki/Changes/IDNA2008">https://fedoraproject.org/wiki/Changes/IDNA2008</a>

Change owner(s):
* Nikos Mavrogiannopoulos <nmav AT redhat DOT com>
* Robert Scheck <robert AT fedoraproject DOT org>

The proposed change is about deprecating libidn, which supports
IDNA2003, and switch all applications using libidn, to libidn2 2.0.0,
which supports IDNA2008.

== Detailed Description ==
Internationalized domain names exist for quite some time (IDNA2003),
although the protocols describing them have evolved in an incompatible
way (IDNA2008).

Reminder meeting : Modularity WG (once every two weeks)

Dear all,

You are kindly invited to the meeting:
Modularity WG (once every two weeks) on 2017-04-04 from 15:00:00 to 16:00:00 UTC
At <a href="mailto:fedora-meeting- ... at irc dot freenode.net">fedora-meeting- ... at irc dot freenode.net</a>

The meeting will be about:
Meeting of the Modularity Working Group.

More information available at: [Modularity Working Group wiki page](<a href="https://fedoraproject.org/wiki/Modularity_Working_Group" title="https://fedoraproject.org/wiki/Modularity_Working_Group">https://fedoraproject.org/wiki/Modularity_Working_Group</a>)

The agenda for the meeting is available at [modularity-wg-agendas pad](<a href="http://piratepad.net/modularity-wg-agendas" title="http://piratepad.net/modularity-wg-agendas">http://piratepad.net/modularity-wg-agendas</a>).

Source: <a href="https://apps.fedoraproject.org/calendar/meeting/5249/" title="https://apps.fedoraproject.org/calendar/meeting/5249/">https://apps.fedoraproject.org/calendar/meeting/5249/</a>

Fedora 26 Alpha RC1.7 has been declared as GOLD and the status is GO

On the third round of Fedora 26 Alpha Go/No-Go Meeting, has just been
Fedora 26 Alpha RC1.7 declared as GOLD.
GA of this release is planed on Tuesday 2017-April-04.

Meeting details can be seen here:
Minutes: <a href="https://meetbot.fedoraproject.org/fedora-meeting-2/2017-03-30/f26-alpha-go-no-go-meeting-3rd.2017-03-30-17.00.html" title="https://meetbot.fedoraproject.org/fedora-meeting-2/2017-03-30/f26-alpha-go-no-go-meeting-3rd.2017-03-30-17.00.html">https://meetbot.fedoraproject.org/fedora-meeting-2/2017-03-30/f26-alpha-...</a>
Log: <a href="https://meetbot.fedoraproject.org/fedora-meeting-2/2017-03-30/f26-alpha-go-no-go-meeting-3rd.2017-03-30-17.00.log.html" title="https://meetbot.fedoraproject.org/fedora-meeting-2/2017-03-30/f26-alpha-go-no-go-meeting-3rd.2017-03-30-17.00.log.html">https://meetbot.fedoraproject.org/fedora-meeting-2/2017-03-30/f26-alpha-...</a>

Thanks everyone who participated on this Alpha release!

Regards,
Jan

Reminder meeting : Fedora 26 Alpha Go/No-Go Meeting

Dear all,

You are kindly invited to the meeting:
Fedora 26 Alpha Go/No-Go Meeting on 2017-03-30 from 17:00:00 to 19:00:00 UTC
At <a href="mailto:fedora-meeting- ... at irc dot freenode.net">fedora-meeting- ... at irc dot freenode.net</a>

The meeting will be about:
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.

F27 Self Contained Change: Replace Yumex-DNF with dnfdragora

= Proposed Self Contained Change: Replace Yumex-DNF with dnfdragora =
<a href="https://fedoraproject.org/wiki/Changes/Replace_yumex-dnf_with_dnfdragora" title="https://fedoraproject.org/wiki/Changes/Replace_yumex-dnf_with_dnfdragora">https://fedoraproject.org/wiki/Changes/Replace_yumex-dnf_with_dnfdragora</a>

Change owner(s):
* Björn Esser <besser82 AT fedoraproject DOT org>
* Christian Dersch <lupinix AT fedoraproject DOT org>

Replace the current alternative graphical package manager.

== Detailed Description ==
Yumex-DNF needs a replacement, since upstream stopped development[1].
With dnfdragora[2] we have a versatile (Qt, GTK and NCurses interface)
replacement.

[1] <a href="https://github.com/timlau/yumex-dnf/blob/develop/README.md" title="https://github.com/timlau/yumex-dnf/blob/develop/README.md">https://github.com/timlau/yumex-dnf/blob/develop/README.md</a>
[2] <a href="https://github.com/manat" title="https://github.com/manat">https://github.com/manat</a>

Fedora 26 Alpha status is NO-GO

The result of the second Fedora 26 Alpha Go/No-Go Meeting is NO-GO.

Due to blockers found during the last days [1] we have decided to
delay the Fedora 26 Alpha release for one more week.

Reminder meeting : Fedora 26 Alpha Go/No-Go Meeting - 2nd round

Dear all,

You are kindly invited to the meeting:
Fedora 26 Alpha Go/No-Go Meeting - 2nd round on 2017-03-23 from 17:00:00 to 19:00:00 UTC
At <a href="mailto:fedora-meeting- ... at irc dot freenode.net">fedora-meeting- ... at irc dot freenode.net</a>

The meeting will be about:
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.

Fedora 26 Alpha Go/No-Go Meeting - the 2nd round on Thursday, March 23 @ 17:00 UTC

Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 26
Alpha.

The meeting is going to be held on Thursday, March 23, 2017 at 17:00
UTC.

Reminder meeting : Modularity WG (once every two weeks)

Dear all,

You are kindly invited to the meeting:
Modularity WG (once every two weeks) on 2017-03-21 from 15:00:00 to 16:00:00 UTC
At <a href="mailto:fedora-meeting- ... at irc dot freenode.net">fedora-meeting- ... at irc dot freenode.net</a>

The meeting will be about:
Meeting of the Modularity Working Group.

More information available at: [Modularity Working Group wiki page](<a href="https://fedoraproject.org/wiki/Modularity_Working_Group" title="https://fedoraproject.org/wiki/Modularity_Working_Group">https://fedoraproject.org/wiki/Modularity_Working_Group</a>)

The agenda for the meeting is available at [modularity-wg-agendas pad](<a href="http://piratepad.net/modularity-wg-agendas" title="http://piratepad.net/modularity-wg-agendas">http://piratepad.net/modularity-wg-agendas</a>).

Source: <a href="https://apps.fedoraproject.org/calendar/meeting/5249/" title="https://apps.fedoraproject.org/calendar/meeting/5249/">https://apps.fedoraproject.org/calendar/meeting/5249/</a>

Fedora 26 Alpha status is NO-GO

Release status of the Fedora 26 Alpha Go/No-Go Meeting is NO-GO.

Due to late blockers we are missing RC of Fedora 26 Alpha release.

Reminder meeting : Fedora 26 Alpha Release Readiness Meeting

Dear all,

You are kindly invited to the meeting:
Fedora 26 Alpha Release Readiness Meeting on 2017-03-16 from 19:00:00 to 21:00:00 UTC
At <a href="mailto:fedora-meeting- ... at irc dot freenode.net">fedora-meeting- ... at irc dot freenode.net</a>

The meeting will be about:
We will meet to make sure we are coordinated and ready for the Alpha release of Fedora 26.

Reminder meeting : Fedora 26 Alpha Go/No-Go Meeting

Dear all,

You are kindly invited to the meeting:
Fedora 26 Alpha Go/No-Go Meeting on 2017-03-16 from 17:00:00 to 19:00:00 UTC
At <a href="mailto:fedora-meeting- ... at irc dot freenode.net">fedora-meeting- ... at irc dot freenode.net</a>

The meeting will be about:
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.

Fedora 26 Alpha Release Readiness Meeting on Thursday, March 16 @ 19:00 UTC

Join us on irc.freenode.net in #fedora-meeting-2 for the Fedora 26
Alpha Release Readiness Meeting meeting.

The meeting is going to be held on Thursday, March 16, 2017 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 Alpha
release of Fedora 26.

Fedora 26 Alpha Go/No-Go Meeting on Thursday, March 16 @ 17:00 UTC

Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 26
Alpha.

The meeting is going to be held on Thursday, March 16, 2017 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.