Ruby Release Goals for Debian Jessie

This page summarizes some ideas about possible goals for Ruby in Jessie:

Key:

Ruby 1.8 removal

Transition tracker: http://release.debian.org/transitions/html/ruby1.8-removal.html

collaborative TODO list: http://titanpad.com/ruby18-removal-triage

Bugs reported: http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-ruby@lists.debian.org;tag=ruby18-removal

Status

Item

Who

Comments

DONE

Drop Ruby 1.8 support from gem2deb

terceiro

done since 0.5.0

TODO

Identify packages with hard dependency on ruby1.8 and file bugs

gwolf

deiv: I found this ones looking at ruby2.0 rebuild results

TODO

Make sure non-leaf packages are fixed

boutil

this is not about doing all the work alone, but tracking the progress and poking people

DONE

special case: KDE ruby packages now build against Ruby1.9.1

boutil

qt-ruby (520901) and korundum (723634)

TODO

identify remaining Ruby 1.8-only packages probably throw them away

gwolf

TODO

Request removal of ruby1.8

PENDING

add extra lintian checks for Ruby packages (see below)

JonasGenannt/hggh

2.5.21 will obsolete ruby 1.8

TODO

decide what to do with the rubygems package (1.8-only)

options are either 1) get rid of it or 2) make it version-independent so it works with whatever interpreter. Problem is if rubygems is older than the version embedded in the interpreter package it may cause problems

New lintian checks for Ruby-related packages:

Ruby 2.0

Status

Item

Who

Comments

DONE

ruby2.0

terceiro

in unstable now

DONE

add gem2deb support for ruby2.0

terceiro

gem2deb 0.5.0 in unstable

DONE

file bugs against packages that fail to build with the new gem2deb+ruby2.0

?DavidSuárez

bugs filed build logs of a rebuild of all packages that build-depend on gem2deb List of failures

TODO

track the bugs against packages that FTBFS with new gem2deb+ruby2.0

?DavidSuárez

3 remaining

TODO

make ruby2.0 default in jessie

terceiro

TODO

decide whether to drop ruby 1.9 as well (see below for points raised)

terceiro (will appreciate everyone's input)

Issues to analyze with regard to dropping ruby 1.9 or not:

Other interpreters

Status

Item

Who

Comments

TODO

Rubinius

terceiro (WILL APPRECIATE HELP) ?DavidSuárez

WIP in git, probably already outdated wrt upstream. Updated to last git commit, links against debian packaged libs, builds (atm) with 1.9 only support, what to do with packaged gems ?

PENDING

JRuby

?DavidSuárez

Tom Marble, of debian-java team, is working on it

Finish transition to new Ruby policy

Status

Item

Who

Comments

TODO

track remaining untransitioned packages and file bugs; adopt/hijack/salvage in the team or NMU or RM

boutil, gwolf

TODO

update ruby-policy package (paulvt suggested converting it to pandoc) and publish

boutil

gem2deb improvements

TODO

fix remaining bugs, or mark the unfeasible ones as WONTFIX

it would be nice to use this as a way of getting new people in gem2deb maintainance

TODO

process ./TODO list in the git repository

ditto

TODO

integrate with autopkgtest

some experiments by lunar

TODO

automatically build and ship developer docs

avtobiff

please try to solve the issue of embedded jquery as part of this. See below for notes from the discussion. See also ruby-debian-doc which is an unfinished proposal on a tool to automatically generate documentation from installed packages

Issues on handling jquery embedded in autogenerated documentation:

Coordination

Status

Item

Who

Comments

TODO

Organize a (periodic?) Ruby team sprint

boutil

the first one will be in Paris just before the Paris MiniDebConf

TODO

Organize monthly IRC meetings

terceiro

for reviewing progress and discussing things in general

Outreach

Status

Item

Who

Comments

TODO

Coordinate an initiative for getting more people in the team. maybe together with the general Debian mentoring initiative

we already get many RFS mails, maybe just more manpower for handling them

TODO

Coordinate PR about the state of Ruby in Debian

coverage on Ruby Weekly News woud be nice

TODO

Create a "Ruby Development" task

more useful than having a live image, and makes creating a live image easier if needed

QUESTION: [terceiro] crazy idea: would we want to work on a Debian Ruby Live/Install DVD to demonstrate the team's work? The idea would be to boot a system with everything you need to start developing Ruby and Rails right away, including nice editors, all the libraries and programs one would need.

Documentation

Status

Item

Who

Comments

TODO

Review existing team documentation in the wiki and propose a way of improving the doc itself and its maintainability

TODO

Give special love to documentation for newcomers on how to get involved and contribute

TODO

Figure out and document how to deal with packaging of apps that rely on bundler/Gemfile/etc