CC Meeting Exec 20070403
Contents
Executive Summary of Commit Committee Meeting 2007-04-03
Full transcript of meeting here: Chat CC Meeting 2007-04-03
Participants (alphabetical order)
- AFalcone
- CarlosRuiz
- croo
- jsSolutions
- teo_sarca
- trifon
- vpj-cd
Summary of Discussion
Strategy for release 3.2
It was discussed in the meeting a change in the strategy for stable release.
Currently there are bugs with priority 9 but very low impact in the system, because they affect a beta functionality (like non-standard costing), or because they affect a specific module not widely used (like webstore).
The agreement was to use the field Group in sourceforge bugs to mark the impact of the bug as:
- Core
- Beta
- Module Specific
- Report
The big impact bugs will be priority 9 on core.
Other bugs can be treated as Known Issues of the release.
Some discussion about the status of costing
There was some discussion about the status of costing.
Looks like the only really supported costing method is Standard Costing. The other methods can be treated as beta status.
Other methods can have issues because the need of reposting in some ordered way, and ordered way can't be achieved in the current code.
Proposal to package migration scripts
It was a proposal to package all migration scripts and integrate it into binaries Adempiere download. Or also to release an independent package on migration section of sourceforge.
