Well, in PETSc (not petsc4py) we have a rather strict rule. Any change that goes to release-maint is immediately merged to -dev. But we never introduce new features in release-maint.
On Fri, May 15, 2009 at 4:04 PM, Dag Sverre Seljebotn <[email protected]> wrote: >> Hi, >> >> the large number of major changes in cython-devel induces a number of >> merge >> conflicts in cython-unstable. I'm very happy to see all those great >> improvements all over the place, but could those who implemented them >> please try to re-integrate them with the unstable branch? > > At least for what I should be doing: Because of time constraints I need to > keep focus on cython-devel myself; I'll be happy to merge next week after > the release is done. > > I don't think what's happened in -devel is a blocker for anything that > should happen in unstable the next week? > > Dag Sverre > > _______________________________________________ > Cython-dev mailing list > [email protected] > http://codespeak.net/mailman/listinfo/cython-dev > -- Lisandro Dalcín --------------- Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC) Instituto de Desarrollo Tecnológico para la Industria Química (INTEC) Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET) PTLC - Güemes 3450, (3000) Santa Fe, Argentina Tel/Fax: +54-(0)342-451.1594 _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
