Community mailing list archives
Re: OCA project: __unported__ folder considered painfulby
2015-03-11 7:48 GMT-06:00 Markus Schneider <email@example.com>:
Having not working modules in root is ugly. At the moment you see easy in github what module is available for this version. If you need to check each __openerp__ what working and whats not, hurts more then having an __unported__ folder.
I always think it is an subjective appreciation, read a web http or a README.md list section is the same IMHO in terms of "reader" effort.
But, when a merger person (technical guy which execute the merge) expend 2 hours solving a merge issue because unnecesary loss of history, and even worst, commit history because unnecesary (technically speaking) move of folders, "that" is a really waste of time.
But again it is a matter of PoV, I prefer save programming time in favor of "reader" time.
I would remove not working modules complete from the branch. At some time it is totally unclear if we need to migrate them, maybe they are obsolete as the new version supports this feature. Maybe never ever someone find to migrate this module. Or maybe their is a better solution for a problem and we decide to switch on next version.
I do not, I would remove them only if the commit of the removal say explicitally "remove in favor of this feature or because it is obsollete for this this and this."
Camptocamp France SAS, Alexandre Fayolle - Camptocamp