FT/TT meeting minutes October 26th 2011
From ADempiere
Revision as of 11:57, 22 November 2011 by Mar cal westf (Talk) (Created page with 'Wednesday, October 26, 2011 # Attendees #* Karsten Thiemann #* Victor Perez #* Trifon Trifonov #* Joel Stangeland #* Karsten Thiemann #* Teo Sarca #* Mark Ostermann #* Tobias Sc…')
This Wiki is read-only for reference purposes to avoid broken links.
Wednesday, October 26, 2011
- Attendees
- Karsten Thiemann
- Victor Perez
- Trifon Trifonov
- Joel Stangeland
- Karsten Thiemann
- Teo Sarca
- Mark Ostermann
- Tobias Schoeneberg
- Michael McKay
- Moderator: Mario Calderon
- Agenda
- Management of Copyrights (commiters, authors)
- Service Pack release
- Hotfix proces
- Service Pack Distribution
- Management of Copyrights (commiters, authors)
- Due to recent discussion in forums.
- Problem concentration on
- changing/ deleting author in code
- missing author in migr. scripts
- author vs. committer in hg
- We have 3 cases of contributing:
- author has commit rights on our repo. is opening a branch do the feature/bug. he or someone else will integrate => author is in HG history, commiter the same
- transplant from external HG repo. e.g. iDempiere case. i think we should transplant the changes in a branch (the initial author is preserved) => integrate (with integrator name)
- contribution is a zip file in tracker. integrator opens a branch, apply the patch, commit with commiter name. integrator integrates with his name
- In all cases we have the author and integrator name in our mercurial repo.
- It was adopted the following rule:
- author has commit rights on our repo. is opening a branch do the feature/bug. he or someone else will integrate => author is in HG history, commiter the same
- transplant from external HG repo. e.g. iDempiere case. i think we should transplant the changes in a branch (the initial author is preserved) => integrate (with integrator name)
- contribution is a zip file in tracker. integrator opens a branch, apply the patch, commit with commiter name. integrator integrates with his nam
- the author will be responsible for placing code in the header of his authorship, it must be documented with a tracker
- Release log with last committer/ author from code/ tracker
- Service Pack release
- idea is to implement the Service Pack using a tools: http://en.wikipedia.org/wiki/StableUpdate or similar tools to create the release patches.
- It was accorded to read the document and discuss the matter on next meeting.
- Hotfix process
- It was talked about ways of doing it.
- There was no time to discuss it to an end, because we ran out of time.
- For next meeting - clarify who, what, where and when the tracker/patch entries are moved ot the hotfix branch.
- Some fixes are left hanging in limbo for a long time.
- Service Pack Distribution
- not discussed. Left for next meeting.