On 15/02/12 23:58, Graeme Gellatly wrote:
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
extra-addons 6.0
community-certified
untested
extra-addons 6.1
community-certified
untested
extra-addons 6.2
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. Then as they
are certified (merge proposal - drivers and committers or new group
community-certifiers) they are removed from untested and merged in to
community-certified. This will over time remove a lot of crap that no-one
uses, serve as a notice to users that they should not use untested branch, and
notice to developers that while they can certainly work on the modules that it
requires testing to be done, and even more so if it is in the untested of a
prior release.
And then bug reports can be filed on the seperate project, managed by community
for community-certified with no expectations, and a fix it yourself for
untested. It will also give OpenERP a better idea of candidates for inclusion
into Official certified addons.
+1 - Sounds like a great suggestion.
Al
_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-community
More help : https://help.launchpad.net/ListHelp
