|
Size: 2159
Comment:
|
Size: 6255
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 16: | Line 16: |
| || ''PENDING'' || Drop Ruby 1.8 suppor 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 || |
|| ''PENDING'' || Drop Ruby 1.8 support from gem2deb || terceiro || done in git || || ''TODO'' || Identify packages with hard dependency on ruby1.8 and file bugs || gwolf || deiv: I found this looking at ruby2.0 rebuild results http://paste.debian.net/26395/ || || ''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 || |
| 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 || gwolf || || |
| Line 22: | Line 22: |
| || ''TODO'' || add extra lintian checks for Ruby packages (see below) || || || || ''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 || |
|
| Line 23: | Line 25: |
| QUESTION: add lintian checks for packaging depending on ruby1.8? | New lintian checks for Ruby-related packages: * depends on ruby1.8 = ERROR * depends on specific ruby version = WARNING * old naming libfoo-ruby = ERROR |
| Line 28: | Line 34: |
| || ''PENDING'' || ruby2.0 || AntonioTerceiro || mostly done in git || || ''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 || |
|| ''PENDING'' || ruby2.0 || terceiro || mostly done in git || || ''PENDING'' || add gem2deb support for ruby2.0 || terceiro || done in git || || ''TODO'' || file bugs against packages that fail to build with the new gem2deb+ruby2.0 || DavidSuárez || [[http://people.debian.org/~terceiro/tmp/rebuild-ruby2.0/| build logs of a rebuild of all packages that build-depend on gem2deb]] - maybe will do another fresh rebuild - most of them are ruby2.0 test failing and some errors on native extensions || || ''TODO'' || track the bugs against packages that FTBFS with new gem2deb+ruby2.0 || DavidSuárez || || || ''TODO'' || Rubinius || terceiro (WILL APPRECIATE HELP) || WIP in git, probably already outdated wrt upstream || || ''TODO'' || JRuby || DavidSuárez || talk to Java people if they are interested to update their package || || ''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) || || |
| Line 32: | Line 43: |
| QUESTION: is anyone from the Ruby team actually interested in JRuby? | 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 |
| Line 37: | Line 52: |
| || ''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 || || || |
|| ''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 42: | Line 57: |
| * 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 || || || || ''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. |
| Line 48: | Line 70: |
| || ''TODO'' || Organize a (periodic?) Ruby team sprint || || || || ''TODO'' || Organize monthly IRC meetings || || for reviewing progress and discussing things in general || |
|| ''TODO'' || Organize a (periodic?) Ruby team sprint || || together with (or close to) the UK mini-debconf or fosdem 2014 || || ''TODO'' || Organize monthly IRC meetings || terceiro || for reviewing progress and discussing things in general || |
| Line 51: | Line 73: |
| QUESTION: do we want/need a monthly IRC meeting? | == 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
Status |
Item |
Who |
Comments |
PENDING |
Drop Ruby 1.8 support from gem2deb |
terceiro |
done in git |
TODO |
Identify packages with hard dependency on ruby1.8 and file bugs |
gwolf |
deiv: I found this looking at ruby2.0 rebuild results http://paste.debian.net/26395/ |
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 |
TODO |
special case: KDE ruby packages still build for Ruby1.8 only |
|
|
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) |
|
|
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
Other interpreters
Status |
Item |
Who |
Comments |
PENDING |
ruby2.0 |
terceiro |
mostly done in git |
PENDING |
add gem2deb support for ruby2.0 |
terceiro |
done in git |
TODO |
file bugs against packages that fail to build with the new gem2deb+ruby2.0 |
?DavidSuárez |
build logs of a rebuild of all packages that build-depend on gem2deb - maybe will do another fresh rebuild - most of them are ruby2.0 test failing and some errors on native extensions |
TODO |
track the bugs against packages that FTBFS with new gem2deb+ruby2.0 |
?DavidSuárez |
|
TODO |
Rubinius |
terceiro (WILL APPRECIATE HELP) |
WIP in git, probably already outdated wrt upstream |
TODO |
JRuby |
?DavidSuárez |
talk to Java people if they are interested to update their package |
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
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 |
|
together with (or close to) the UK mini-debconf or fosdem 2014 |
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 |
|
|