Talk:Software Development Procedure
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
Contents
Change of terminology for HG
Tobi 17:12, 21 December 2010 (UTC) If we switch to mercurial, the concept is unaffected, there are just some minor differences:
- Instead of developers creating a branch, they clone the repository. That means, they create a local copy of the repo to work with.
- Only PMC is required to have write-access to the mercurial-repo.
- Developers submit their contributions in one of the ways that are described by Carlos here: Branch_GlobalQSS_361#Sending_your_changes_for_peer_review
- Instead of "trunk", we speak of the Default-Branch
- Open question for the current stabilization-branch
- It can still be a branch, similar to svn
- Difference between hg and svn: a branch is not a logical copy that by convention lives under "branches". Instead, it is explicitly created a a branch by the hg branch command.
- Or it can be another HG-repository
- It can still be a branch, similar to svn
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?
- Nwessel 12:15, 18 November 2010 (UTC) I think the technical team can make usage of that rules and apply them to themselfes.
different diagram by kthiemann
- I tried to create a more simple diagram to make the process easier to understand:
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
- Ramiro Vergara
- Christina Ghita
