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. This will help significantly with the stable
branch, which revs the minor release fairly often.
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel-announce@lists.fedoraproje…
I would like to announce Insim, which is a new web service for
monitoring package installation sizes and other numbers.
Insim checks installation sizes of defined modules (groups of
packages) and presents this information to user. It's main goal is to
help developers to optimize package dependencies, which aligns with
some objectives of modularization effort.
More information about Insim can be found at [1]. A running Insim
instance hosted at Fedora infrastructure cloud is available at [2].
Note that Insim is still in early development. There are many bugs
and missing features. You can report issues at [3] or directly to me.
[1] https://fedoraproject.org/wiki/Insim
[2] http://insim.fedorainfracloud.org/
[3] https://pagure.io/insim/issues
--
Mikolaj Izdebski
Software Engineer, Red Hat
IRC: mizdebsk
# F24 Blocker Review meeting
# Date: 2016-03-29
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We were quite short on people for the blocker review meeting
today (2016-03-28) so we're going to try again tomorrow (2016-03-29),
same time (16:00 UTC), same channel (#fedora-blocker-review).
We have a few proposed blockers to review, so let's take a
look at them. There are 4 proposed Beta blockers, 5 proposed Final
blockers, and 2 accepted Beta blockers.
If you have time tonight, you can take a look at the proposed or
accepted blockers before the meeting -Â Â the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/Â . Remember to check
each outstanding milestone (Beta and Final).
We'll be evaluating these bugs to see if they violate any of theÂ
Release Criteria and warrant the blocking of a release if they're notÂ
fixed. Information on the release criteria for F24 can be found on theÂ
wiki [0].
For more information about the Blocker and Freeze exception process,Â
check out these links:
 - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
 - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review MeetingÂ
works - or how it's supposed to go and you want to run one - check outÂ
the SOP on the wiki:
 - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good night and see you tomorrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
test-announce mailing list
test-announce(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/test-announce@lists.fedoraprojec…
Hi All,
I just noticed that the Upstream Projects Schedule section on the below
page (Fedora 24 release schedule page) on wiki is not updated for Fedora
24. Is it intentional?
https://fedoraproject.org/wiki/Releases/24/Schedule
Thanks.
--
Regards,
Sumit Bhardwaj
We have 11 nominations[1], more than the typical 7, for the voting
members of the Modularity WG already and I have a few full-time
developers who have been starting to do some work on modularity. As we
have a number of people expressing early interest, I would like to get
the WG moving now. We can keep the nominations open until April 18th,
but maybe we can start moving forward even before then.
I would like to hold the first meeting with the nominees and any other
interested participants on Mar. 31 15h/3pm UTC in #fedora-meeting.
Please come and join us!
Langdon
Modularity Objective Lead
[1]:
https://fedoraproject.org/wiki/Modularity_Working_Group/Initial_Nominations…