[pymvpa] Change of repository layout

Yaroslav Halchenko debian at onerussian.com
Mon Sep 29 15:26:29 UTC 2008

> > 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.
ok, bought it

> > >   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?
it would be "cleaner" to my taste... so everything etch related is under
etch... it is the same issue as with svn organization -- either you keep
projects on top level and trunk,tags,branches below each project, or you
have trunk/tags/branchs on top of the projects. Imho the former is
nicer since everything project related is within the same directory.

Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers-Newark
Student  Ph.D. @ CS Dept. NJIT
Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171
        101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102
WWW:     http://www.linkedin.com/in/yarik        

More information about the Pkg-ExpPsy-PyMVPA mailing list