[Pkg-zsh-devel] zsh_5.2-dev-1-1_amd64.changes ACCEPTED into experimental

[Axel Beckert]

Hi again,

Axel Beckert wrote:
> Daniel Shahaf wrote:
> > >    * [86ca06fb] Import new upstream beta release.
> > zsh 5.2-dev-1 is not a beta release.  The version number was changed
> > (incremented) as a convenience for users of zsh from master, but does
> > not indicate a more-stable tree.
> > 
> > The version number is changed whenever a non-backwards-and-forwards-compatible
> > change to generating/parsing of *.zwc files is made, to prevent post-change
> > zsh from reading a *.zwc file generated by pre-change zsh (or vice-versa).
> 
> Thanks for that information. I already wondered why nobody talked
> about it.

So I wonder how's the best way to get the packaging-features in that
upload into unstable. I see the following possibilities:

* Upload 5.2-dev-1 to unstable -- means a non-released inbetweenish
  version would get to unstable. Clearly not my preferred solution.

* Branch out a temporary branch called e.g. stretch or unstable or so
  just before I imported 5.2-dev-1 and then cherry-pick all packaging
  related commits. Not sure if there's a need to merge them back into
  master when the next upstream release (either 5.2.1 or 5.3) is out.
  (Not sure what jenkins-debian-glue does with arbitrary branch
  names -- probably try to build something from them.)

* Just wait for the next upstream release (either 5.2.1 or 5.3) and
  then upload it to unstable -- in the hope that this long enough
  before the freeze.

Anyone has a clue when to expect the next upstream release? That'd
make that decision much easier. :-)

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE