[pymvpa] Change of repository layout

Michael Hanke michael.hanke at gmail.com
Sat Sep 27 19:26:13 UTC 2008

On Sat, Sep 27, 2008 at 03:16:34PM -0400, Yaroslav Halchenko wrote:
> > maint/?.?
> >   Upstream maintenance branches. Bugfixes and documentation enhancements
> >   for the current ?.? release go here and will later on be released as
> >   ?.?.? minor releases.
> I am not clear on what would be a destiny of this one... bug fixes
> usually go into some master and later cherry picked or just merged into
> main master...
There is no change in what we do now -- if a release needs fixes it gets
fixes in maint/?.? which can then be merged into any other branch
(including master). I consider merging superior to cherry-picking, as
you can better track whether a particular change went into a branch.

> >   For releases in Debian proper we would usually only have a
> >   'dist/debian/proper/sid' branch that contains the most recent upstream
> may be better to have dist/debian/{etch,sid}/{bp,proper} ? ie flip two
> levels?
What would be the advantage?

> >   For simplicity I would simply put stuff like 'hardy' and 'gutsy' under
> >   'dist/debian/bp/' as well. There is not really a differences wrt
> >   the environment.
> agree... especially since ubuntu people might introduce their
> 'improvement' changes (ie changes of maintainer and adding 'support' for
> python 100.0 prior to its release), so our ubuntu packaging would
> diverge from theirs
> > Morever, IMHO we can keep the current tag scheme: upstream/<version> for
> > upstream releases and debian/<debian_version> for Debian packages.
> how do we tag release/backport specific tags? add it into the version
> string?
Same as debian version string would be, ie. 0.2.2-1etch2
For backports this might not be necessary, as we would probably do a
proper new release -- but this is not required.


GPG key:  1024D/3144BE0F Michael Hanke
ICQ: 48230050

More information about the Pkg-ExpPsy-PyMVPA mailing list