c2c-oerpscenario team mailing list archive

[Phong Nguyen-Thanh <772360@xxxxxxxxxxxxxxxxxx>]

I think the current process is that a new (community) module should be
placed into addons-extra or addons-community and when it's matured or
OpenERP SA decided it would be usefull to get promoted to addons and
will include in OPW in the coming release. Thus if OpenERP decide to
move, they should make the clean-up and it's even better if they send
out the notification.

I think these residual is more likely a result of neglect/oversight in
the promotion/release procedure, which should be fixed so that it will
reduce the maintenance cost for OpenERP and the community.

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/772360

Title:
  [6.0 series] duplicate modules in addons and addons-extra

Status in OpenERP Modules (addons):
  New

Bug description:
  The following modules exist both in addons and addons-extra branches
  (of 6.0.x series). If modules are promoted from addons-extra to addons
  branch, they should be removed from the addons-extra to avoid
  confusion and (perhaps) wrong commit/fix.

  account_anglo_saxon/
  account_coda/
  base_crypt/
  base_module_doc_rst/
  caldav/
  hr_evaluation/
  hr_payroll/
  l10n_ma/
  lunch/
  marketing/
  multi_company/
  point_of_sale/
  product_expiry/
  product_visible_discount/
  sale_layout/
  sale_margin/
  stock_planning/
  survey/
  thunderbird/
  users_ldap/