[Pkg-octave-devel] Updating the packages on RC-unrelated issues

[Rafael Laboissiere]

Ok, I just fixed Bug#681065 and, in the process, created the experimental
branch in the Git repository for the octave package.

Using "gbp-clone --all" will create a local branch "experimental" which
is set up to track "origin/experimental".  Otherwise, after git pull, I
guess that the following commands will be enough:

    git branch experimental origin/experimental
    git checkout experimental 
    
Rafael

* Sébastien Villemot <sebastien.villemot at ens.fr> [2012-07-12 16:59]:

> Jordi Gutiérrez Hermoso <jordigh at octave.org> writes:
> 
> > I wish Debian's release cycle didn't change the de-facto meaning of
> > unstable and experimental during freeze time. I wish that during
> > freeze time, a new wheezy-proposed or whatever branch was created and
> > unstable and experimental kept the same meaning.
> >
> > Sadly, instead experiemental becomes the new unstable and unstable
> > becomes "wheezy-backports" or "wheezy-proposed". It has to be done
> > this way. It's how everyone else in Debian does it. So yes, this is
> > what happens.
> 
> The fundamental reason is that packages that enter wheezy via unstable
> get more testing (10 days) than packages that enter via
> testing-proposed-updates (which are basically not tested by anyone else
> than the developer). If we want a quality release we have to use
> unstable as a staging area for stable during the freeze.
> 
> A second reason, which is more social than technical, is that developers
> may be more inclined to fix RC bugs in other packages during the freeze
> if they cannot use unstable as a playground for the latest release of
> their pet package.
> 
> So yes, this is more or less unavoidable, even if I understand (and
> share to some extent) your frustration.