Differences between revisions 7 and 9 (spanning 2 versions)
Revision 7 as of 2013-08-16 10:23:12
Size: 3302
Comment:
Revision 9 as of 2013-08-16 10:24:16
Size: 3318
Comment:
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:
|| ''TODO'' || identify Ruby 1.8-only packages probably throw them away || || || || ''TODO'' || identify remaining Ruby 1.8-only packages probably throw them away || || ||
Line 46: Line 46:
|| ''TODO'' || process ./TODO list in the git repository || || || || ''TODO'' || process ./TODO list in the git repository || || ditto ||

Ruby Release Goals for Debian Jessie

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

Key:

  • TODO = not done

  • PENDING= (mostly?) done, but not in the archive yet

  • DONE = done and in the archive

Ruby 1.8 removal

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

Status

Item

Who

Comments

PENDING

Drop Ruby 1.8 support from gem2deb

AntonioTerceiro

done in git

TODO

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

TODO

Make sure non-leaf packages are fixed

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

TODO

special case: KDE ruby packages still build for Ruby1.8 only

TODO

identify remaining Ruby 1.8-only packages probably throw them away

TODO

Request removal of ruby1.8

QUESTION: add lintian checks for packaging depending on ruby1.8?

Other interpreters

Status

Item

Who

Comments

PENDING

ruby2.0

AntonioTerceiro

mostly done in git

PENDING

add gem2deb support for ruby2.0

AntonioTerceiro

done in git

TODO

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

build logs of a rebuild of all packages that build-depend on gem2deb

TODO

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

TODO

Rubinius

AntonioTerceiro (WILL APPRECIATE HELP)

WIP in git, probably already outdated wrt upstream

TODO

JRuby

talk to Java people if they are interested to update their package

QUESTION: is anyone from the Ruby team actually interested in JRuby?

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

TODO

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

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

Coordination

Status

Item

Who

Comments

TODO

Organize a (periodic?) Ruby team sprint

TODO

Organize monthly IRC meetings

for reviewing progress and discussing things in general

QUESTION: do we want/need a monthly IRC meeting?

Outreach

TODO

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

TODO

Coordinate PR about the state of Ruby in Debian

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.