Hi, On Wed, Jun 17, 2015 at 05:02:24PM +0100, Jonathan Wiltshire wrote: > Control: tag -1 moreinfo > > On 2015-06-17 16:08, Antonio Terceiro wrote: > >This transition will be used to track which packages need to be rebuilt > >with Ruby 2.2 suport before we make it the default. Ruby 2.1 is still > >supported, and only after 2.2 becomes the default we will start another > >transition to phase 2.1 out. > > Please stage the transition in experimental first, and come back when it's > clearer what needs to be done.
We already know what needs to be done, since the transitions from 1.9 to 2.0 and from 2.0 to 2.1 were done in a very similar way. We do the transition in phases so that unstable is never broken: - phase 0: the new ruby reaches unstable - phase 1: ruby-defaults gets uploaded telling gem2deb to build for both the old and the new ruby versions. - phase 2: packages get rebuilt/fixed with support for both the old ruby and the new ruby this is where we are now what needs to fixed is usually fixed in a way that it won't need to be fixed again in the next transition. In fact, the last transition was a lot smoother than the previous one. - phase 3: new ruby becomes the default - phase 4: ruby-defaults gets uploaded telling gem2deb to stop building for the old ruby - phase 5: packages get rebuilt/fixed to drop support for the old ruby - phase 6: old ruby gets removed -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: Digital signature
