Difference between revisions of "Talk:Software Development Procedure"
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
| Line 1: | Line 1: | ||
==open questions by nwessel== | ==open questions by nwessel== | ||
* do we need to revise the best practices | * do we need to revise the best practices | ||
| − | ** [[User:Tobi| | + | ** [[User:Tobi|tobi42]] 08:06, 18 November 2010 (UTC) Here is my opinion |
**#I don't think that the best practices should be written in stone (im am bit sceptical about the "100% compliance" thing, too). It should be up to the PMC teams to interpret and revise them as neccessary. | **#I don't think that the best practices should be written in stone (im am bit sceptical about the "100% compliance" thing, too). It should be up to the PMC teams to interpret and revise them as neccessary. | ||
**#Therefore I don't think that the ABP need a resivion before this whole thing can start. They are already pretty good to help both the developers in writing good code and the PMC team to do a good review. | **#Therefore I don't think that the ABP need a resivion before this whole thing can start. They are already pretty good to help both the developers in writing good code and the PMC team to do a good review. | ||
* provide templates and samples for wiki pages | * provide templates and samples for wiki pages | ||
| + | ==open questions by tobi42== | ||
| + | *I think we should include the [[Release Commit Rules]] in the concept. The technical team should only commit stuff to the stabilization-branch, if it meets those rules. This implies that work from a developer branch is only merged into stabilization branch, if those rules are met. WDYT? | ||
Here is the list of people working on the concept and agreeing with it: | Here is the list of people working on the concept and agreeing with it: | ||
Revision as of 01:24, 18 November 2010
open questions by nwessel
- do we need to revise the best practices
- tobi42 08:06, 18 November 2010 (UTC) Here is my opinion
- I don't think that the best practices should be written in stone (im am bit sceptical about the "100% compliance" thing, too). It should be up to the PMC teams to interpret and revise them as neccessary.
- Therefore I don't think that the ABP need a resivion before this whole thing can start. They are already pretty good to help both the developers in writing good code and the PMC team to do a good review.
- tobi42 08:06, 18 November 2010 (UTC) Here is my opinion
- provide templates and samples for wiki pages
open questions by tobi42
- I think we should include the Release Commit Rules in the concept. The technical team should only commit stuff to the stabilization-branch, if it meets those rules. This implies that work from a developer branch is only merged into stabilization branch, if those rules are met. WDYT?
Here is the list of people working on the concept and agreeing with it:
- Teo Sarca
- Joel Stangeland
- Victor Perez
- Werner Scharinger
- Thomas Kreser
- Mario Calderon
- Susanne Calderon
- Kai Schaeffer
- Karsten Thiemann
- Mark Ostermann
- Norbert Wessel
- Tobias Schöneberg
- Dirk Niemeyer
- Dominik Zajac
