730
Comment:
|
6968
info about the january Ruby meeting + info about autopkgtest experiment by lunar
|
Deletions are marked like this. | Additions are marked like this. |
Line 5: | Line 5: |
== Interpreters == * deprecate Ruby 1.8 * identify Ruby 1.8-only packages and probably throw them away * finish packaging for alternative interpreters * Ruby 2.0 (high priority) * Rubinius * JRuby (talk to Java people if they are interested to update their package) |
Key: |
Line 13: | Line 7: |
== Transition to new Ruby policy == * track remaining untransitioned packages and file bugs/(NMU?) * KDE ruby packages e.g. still build for Ruby1.8 (only) * update ruby-policy package (paulvt suggested converting it to pandoc) and publish |
* ''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 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: [[http://paste.debian.net/26648/|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 || || ''PENDING'' || special case: KDE ruby packages still build for Ruby1.8 only || boutil || bugs + patches filed for qt-ruby (DebianBug:520901) and korundum (DebianBug:723634)|| || ''TODO'' || identify remaining Ruby 1.8-only packages probably throw them away || gwolf || || || ''TODO'' || Request removal of ruby1.8 || || || || ''TODO'' || add extra lintian checks for Ruby packages (see below) || JonasGenannt/hggh || || || ''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: * depends on ruby1.8 = ERROR * depends on specific ruby version = WARNING * old naming libfoo-ruby = ERROR == 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 || [[http://udd.debian.org/cgi-bin/bts-usertags.cgi?user=debian-ruby%40lists.debian.org&tag=ruby2-ftbfs-20130818| bugs filed]] [[http://aws-logs.debian.net/ftbfs-logs/ruby2.0/| build logs of a rebuild of all packages that build-depend on gem2deb]] [[http://paste.debian.net/26715/|List of failures]] || || ''TODO'' || track the bugs against packages that FTBFS with new gem2deb+ruby2.0 || DavidSuárez || || || ''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: * We should expect jessie to freeze on mid-2014 * we don't known for how long we will have upstream support. * the time between the releases of 1.9 and 2.0 was a lot shorter than the time between 1.8 and 1.9 == 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 || || |
Line 18: | Line 62: |
== gem2deb improvements == | |
Line 19: | Line 64: |
== gem2deb improvements == * fix remaining bugs * process TODO list |
|| ''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 || || [[https://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2013-September/016366.html|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 [[http://anonscm.debian.org/gitweb/?p=pkg-ruby-extras/ruby-debian-doc.git;a=summary|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: * usual procedure: in debian/rules, we usually replace the embedded jquery with a symlink to the one from the libjs-jquery package. * it was said that packages should not depend on jquery, because if install recommends is enabled (it is by default) you might get apache and all the rest * [terceiro] actually apache will only be brought in if install '''suggests''' is enabled. It will bring stuff such as wwwconfig-common which you probably do not want when installing a ruby package with documentation. == Coordination == || Status || Item || Who || Comments || || ''TODO'' || Organize a (periodic?) Ruby team sprint || boutil || the first one will be in [[../Meeting/Paris2014|Paris]] just before the [[https://wiki.debconf.org/wiki/Miniconf-Paris/2014|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 || || || |
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
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 |
|
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 |
PENDING |
special case: KDE ruby packages still build for Ruby1.8 only |
boutil |
bugs + patches filed for 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 |
|
|
TODO |
add extra lintian checks for Ruby packages (see below) |
JonasGenannt/hggh |
|
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:
- depends on ruby1.8 = ERROR
- depends on specific ruby version = WARNING
- old naming libfoo-ruby = ERROR
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 |
|
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:
- We should expect jessie to freeze on mid-2014
- we don't known for how long we will have upstream support.
- the time between the releases of 1.9 and 2.0 was a lot shorter than the time between 1.8 and 1.9
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 |
|
|
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:
- usual procedure: in debian/rules, we usually replace the embedded jquery with a symlink to the one from the libjs-jquery package.
- it was said that packages should not depend on jquery, because if install recommends is enabled (it is by default) you might get apache and all the rest
[terceiro] actually apache will only be brought in if install suggests is enabled. It will bring stuff such as wwwconfig-common which you probably do not want when installing a ruby package with 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 |
|
|