On Thursday 16 February 2012, Graeme Gellatly wrote: > to my mind extra-addons suffers a major issue which just worsens with each > version. That is you never know if it has been ported to work on the > current version. > > What I would like to see is a community maintained extra-addons branch > structure - completely seperate from openobject-addons that looks > something like this. > > extra-addons 5.0 > community-certified > untested > > then with each release only the community-certified addons of the previous > release are ported to the untested branch of the next release.
Moving files would be a bit messy, IMHO. It might interfere with VCS merges, confuse translations etc. I'd suggest to use some kind of *flag* for untested/broken modules. Just put it inplace w/o any API change (ie. maintain 6.0 compatibility) and then update the flag as these modules get ported or broken again. -- Say NO to spam and viruses. Stop using Microsoft Windows! _______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
