* Betr.: " Re: [tryton-dev] Staging modules" (Thu, 5 Jan 2012 00:04:19 +0100):
> On 04/01/12 23:08 +0100, Mathias Behrle wrote:
> > * Betr.: " [tryton-dev] Staging modules" (Wed, 4 Jan 2012 12:34:38 +0100):
> > > I got some modules written for 2.2 that are in codereview since a long
> > > time now.
> > > Some of them can not be put in the base sets of 2.2 like
> > > "sale_shipment_cost_weight" because of the glue code it contains (see
> > > previous thread).
> > > But I don't think it is good to let modules in codereview for so long.
> >
> > Why?
>
> Because I have the feeling that in such cases we are using codereview
> like a VCS but mercurial is a better one.
> And it makes the testing process more complicated and I think people are
> just reviewing the code but not really run it.
>
> > > So I propose to create a staging directory for 2.2 (and also trunk) to
> > > put such modules. This will mean that you can use them for this series
> > > but there will be no migration and limited support for them until they
> > > reach the base.
> >
> > For me it is not good to create dead ends. There are already enough
> > questions about uninstallation of modules, there will be more with such a
> > layout.
>
> It is already as the code is there (on codereview) and people already
> starts to use it.
Taking code from a *codereview* is really different from taking it from
tryton.org. If you want absolutely have it in a mercurial repos you could
publish it either at your home at b2ck.org (as you did already) or upload it to
some public hoster (like others do). AFAIS you didn't want a place for other
than finally accepted modules on tryton.org. It should be the same for B2CK
modules.
--
Mathias Behrle
MBSolutions
Gilgenmatten 10 A
D-79114 Freiburg
Tel: +49(761)471023
Fax: +49(761)4770816
http://m9s.biz
UStIdNr: DE 142009020
PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6
signature.asc
Description: PGP signature
