Difference between revisions of "Technical Team"
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
m (proposed agenda 20110210) |
m (→20110203 (together with Functional Team)) |
||
Line 87: | Line 87: | ||
== 20110203 (together with [[Functional Team]]) == | == 20110203 (together with [[Functional Team]]) == | ||
− | [[FT/ | + | [[FT/TT_meeting_minutes_feb_03th_2011|Minutes]] |
== 20110210 (together with [[Functional Team]]) == | == 20110210 (together with [[Functional Team]]) == |
Revision as of 02:50, 10 February 2011
Contents
- 1 Initial Staff
- 2 Responsibilities
- 3 Process
- 4 Concept Template Suggestion
- 5 Meetings of Technical Team
- 5.1 20101209 (together with Functional Team)
- 5.2 20101216 (together with Functional Team)
- 5.3 20110106 (together with Functional Team)
- 5.4 20110113 (together with Functional Team)
- 5.5 20110120 (together with Functional Team)
- 5.6 20110127 (together with Functional Team)
- 5.7 20110203 (together with Functional Team)
- 5.8 20110210 (together with Functional Team)
Initial Staff
- Teo Sarca
- Karsten Thiemann
- Tobias Schöneberg
- Victor Perez (Maintaining Libero MFG and HR only)
- Trifon Trifonov
- <please add your name when you want to join the team (4 hours minimum work per week)>
Everybody can become a team member, unless 2/3 of existing members disagree.
Responsibilities
As described and voted in the Software Development Procedure
- maintains trunk and stabilization branch
- ensures that all contributions meet technical requirements in respect to quality
- code is documented
- backward compatibility is achieved
- migration scripts complete
- technical documentation sufficient
- backward comparability analysis
- migration scripts are provided (when needed)
- regular releases by providing and supporting a release manager from amongst their members
Process
- When a feature in a development branch is ready for approval the developer contacts the technical team and applies for approval
- Technical Team meets on a regular basis and discusses the applications
- If all criteria are met the team approves the feature from a technical perspective and allows the developer to merge his feature into stabilization branch
Concept Template Suggestion
Technical Specification Template
Meetings of Technical Team
We meet at Thursday 15:00 hours GMT via Skype. Minutes of Meetings are to be written on the following Friday latest and published on the wiki page until evening.
20101209 (together with Functional Team)
Agenda Minutes
- Channel for regular meetings
- Frequency of regular meetings
- Rules and rights of every team
- Communication between both teams
- Misc
20101216 (together with Functional Team)
Agenda Minutes
- Review task list from last meeting
- Templates for teams
- Repository (Mercurial)
- Codebase
- Misc
- Next meeting
- Next moderator
20110106 (together with Functional Team)
20110113 (together with Functional Team)
Agenda Minutes
- Review task list from last meeting
- Misc/ Next Steps
- Next meeting
- Next moderator
20110120 (together with Functional Team)
20110127 (together with Functional Team)
Agenda Minutes
- Mercurial direcories
- Patches
- Test framework
- HG Repo Permissions
20110203 (together with Functional Team)
20110210 (together with Functional Team)
Agenda Minutes
- Review task list from last meeting
- Test Framework
- Bug Fixes
- Status of new functionality
- Migration Tool see [1]