Unresponsive maintainer: janfrode
by Björn 'besser82' Esser
Hello,
does anyone here know how to contact janfrode? I can't get him to answer
on rhbz # [1], nor on his email address from FAS.
=== Output of `fedora_active_user.py`: ===
```
Last login in FAS:
janfrode 2014-08-07
Last action on koji:
Sat, 19 Aug 2017 package list entry revoked: altermime in dist-6E-
epel by pkgdb
Last package update on bodhi:
2014-06-14 13:13:42 on package mon-1.2.0-11.el6
```
Thanks,
Björn
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1666720
5 years, 2 months
FINAL REMINDER: Self-Contained Change deadline is Tuesday
by Ben Cotton
This is your final reminder that Self-Contained Change proposals for
Fedora 30 must be submitted (i.e. set to the "Change Ready for
Wrangler") category by the end of the day (UTC) on Tuesday, 29
January.
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
5 years, 2 months
Agenda for Tuesday's Modularity Team Meeting (2019-01-29)
by Nils Philippsen
Find below a list of topics which are planned to be discussed in the
Fedora Modularity Team meeting on Tuesday at 15:00 UTC in
#fedora-meeting-3 on irc.freenode.net.
To find out when this is in your local time zone, check the Fedora
Calendar (if you've set it and are logged in):
https://apps.fedoraproject.org/calendar/modularity/#m5249
Alternatively, to convert UTC to your local time zone, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d 'Tuesday 15:00 UTC'
Links to all issues below can be found at:
https://pagure.io/modularity/report/meeting_agenda
= Discussed and Voted =
Modularity WG Charter (contd.)
https://pagure.io/modularity/issue/119
DECISION (+4, 0, -0)
= Followups =
#topic #112 Discussion: Module lifecycles
#link https://pagure.io/modularity/issue/112
.modularity 112
#link https://pagure.io/fesco/issue/2027
#topic #115 Discussion: Stream branch ownership for packages & modules
#link https://pagure.io/modularity/issue/115
.modularity 115
#link https://pagure.io/fesco/issue/2028
= New business =
N/A
= Open Floor =
For more complete details, please visit each individual
issue. The report of the agenda items can be found at
https://pagure.io/modularity/report/meeting_agenda
If you would like to add something to this agenda, you can file a new
issue at https://pagure.io/modularity/issues, or bring it up at the end
of the meeting during the open floor topic. Note that the meeting is
one hour long and issues we don't get around to discussing may be
deferred until the following meeting.
--
Nils Philippsen "Those who would give up Essential Liberty to
Software Engineer purchase a little Temporary Safety, deserve neither
Red Hat Liberty nor Safety." -- Benjamin Franklin, 1759
PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011
5 years, 2 months
Fedora 30 System-Wide Change proposal: Ruby 2.6
by Ben Cotton
https://fedoraproject.org/wiki/Changes/Ruby_2.6
== Summary ==
Ruby 2.6 is the latest stable version of Ruby. Many new features and
improvements are included for the increasingly diverse and expanding
demands for Ruby. With this major update from Ruby 2.5 in Fedora 29 to
Ruby 2.6 in Fedora 30, Fedora becomes the superior Ruby development
platform.
== Owner ==
* Name: [[User:vondruch| Vít Ondruch]], [[User:pvalena| Pavel Valena]]
* Email: vondruch(a)redhat.com, pvalena(a)redhat.com
== Detailed Description ==
Ruby 2.6 is upstream's new major release of Ruby. Many new features
and improvements are included.
=== JIT ===
Ruby 2.6 introduces an initial implementation of JIT (Just-in-time) compiler.
JIT compiler aims to improve performance of any Ruby program
execution. Unlike ordinary JIT compilers for other languages, Ruby’s
JIT compiler does JIT compilation in a unique way, which prints C code
to a disk and spawns common C compiler process to generate native
code.
The main purpose of this JIT release is to provide a chance to check
if it works for your platform and to find out security risks before
the 2.6 release. JIT compiler is supported when Ruby is built by GCC,
Clang, or Microsoft VC++, which needs to be available on runtime.
Otherwise you can’t use it for now.
As of Ruby 2.6.0 preview3, we achieved 1.7x faster performance than
Ruby 2.5 on CPU-intensive non-trivial benchmark workload called
Optcarrot. The performance on memory-intensive workload like Rails
application are going to be improved as well.
=== RubyVM::AST [Experimental] ===
Ruby 2.6 introduces `RubyVM::AST` module.
This module has `parse` method which parses a given ruby code of
string and returns AST (Abstract Syntax Tree) nodes, and `parse_file`
method which parses a given ruby code file and returns AST nodes.
`RubyVM::AST::Node` class is also introduced. You can get location
information and children nodes from `Node` objects. This feature is
experimental. Compatibility of the structure of AST nodes are not
guaranteed.
=== New Features ===
* Add a new alias `then` to `Kernel#yield_self`.
* Add `Random.bytes`.
* Add `Binding#source_location`. This method returns the source
location of binding, a 2-element array of __FILE__ and __LINE__.
* Add `:exception` option to let `Kernel.#system` raise error instead
of returning `false`.
* Add a new alias then to `Kernel#yield_self`.
* `else` without `rescue` now causes a syntax error. [EXPERIMENTAL]
* Constant names may start with a non-ASCII capital letter.
* An endless range, (1..), is introduced. It works as it has no end.
=== Performance improvements ===
* Speedup `Proc#call` because we don’t need to care about $SAFE any
more. With `lc_fizzbuzz` benchmark it makes x1.4 speed improvement.
* Speedup `block.call` where block is passed block parameter. Ruby 2.6
improves the performance of passed block calling. There can observed
2.6x improvement with micro-benchmarks.
* Transient Heap (theap) is introduced. theap is managed heap for
short-living memory objects which are pointed by specific classes. For
example, making small and short-living Hash object is x2 faster. With
rdoc benchmark, 6-7% performance improvement is observed.
=== Other notable changes since 2.5 ===
* `$SAFE` is a process global state and we can set `0` again.
* Passing `safe_level` to `ERB.new` is deprecated. `trim_mode` and
`eoutvar` arguments are changed to keyword arguments.
* Merged RubyGems 3.0.0.beta2.
* Merge Bundler as default gem.
== Benefit to Fedora ==
With a latest release, Ruby language is supporting the newest language
features, which enables even faster and easier development of Ruby
applications.
== Scope ==
* Proposal owners:
** Finish packaging of Ruby 2.6. Current changes available in PR
https://src.fedoraproject.org/rpms/ruby/pull-request/32
** Rebuilding of Ruby packages providing native extensions (i.e.
packages which depends on libruby).
.
* Other developers:
** Rebuild of packages with binary extensions (i.e. packages which
depends on libruby) will be handled automatically, but some packages
might need fixes/updates to support Ruby 2.6 properly.
* Release engineering: [https://pagure.io/releng/issue/7936 #7936]
** Separate Koji tag for package rebuild will be needed.
* Policies and guidelines: N/A
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
* User specific Ruby binary extensions need to be rebuild.
== How To Test ==
* No special hardware is needed.
* To test, install Ruby 2.6. The test builds are pusblished in PR or
on Ruby-SIG ML
* Try to locally rebuild your packages using Ruby 2.6.
* Use the packages with your applications previously written in Ruby.
* If something doesn't work as it should, let us know.
== User Experience ==
The Ruby programs/scripts should behave as they were used to.
== Dependencies ==
<pre>
$ dnf repoquery --disablerepo=* --enablerepo=rawhide
--enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel' |
sort | uniq | wc -l
156
</pre>
== Contingency Plan ==
* Contingency deadline: Mass Rebuild
* Blocks release? No
* Blocks product? No
== Documentation ==
* [http://www.ruby-doc.org/ Help and documentation for the Ruby
programming language]
* [https://github.com/ruby/ruby/blob/v2_6_0_preview3/NEWS Ruby
2.6.0.preview3 NEWS]
== Release Notes ==
* The Ruby 2.6 bumps soname, therefore Ruby packages, which use binary
extensions, should be rebuilt. Nevertheless, since upstream paid great
attention to source compatibility, no changes to your code are needed.
https://github.com/ruby/ruby/blob/trunk/NEWS
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
5 years, 3 months