When attached to a jira issue, then after approval (or no objection)
merging the patch into the master branch by a committer so difficult?
I am sorry, i do not see a problem here....
Regards,
Hans
On 06/05/15 13:53, Jacopo Cappellato wrote:
On May 6, 2015, at 8:46 AM, Hans Bakker <mailingl...@antwebsystems.com> wrote:
the workflow can be simple as is described in:
http://www.apache.org/dev/git.html
we could use this as the MVP (minimum viable product) so mimic basically how
people use SVN and then slowly take advantage of the possibilities of GIT.
Regards,
Hans
Hans,
I think you didn't spend enough time studying this material.
The document you are referencing is what we already have: the workflow and
infrastructure described are already in place:
1) a writable svn repo
2) a read only mirror in git: git://git.apache.org/ofbiz.git
3) Jira to submit patches
Jacopo
On 06/05/15 13:35, Jacopo Cappellato wrote:
My vote is clearly stated: propose a Git workflow that is inline with the ASF
policies and that is good for the OFBiz project and I will vote positively.
Jacopo
On May 6, 2015, at 8:29 AM, Hans Bakker <mailingl...@antwebsystems.com> wrote:
Then you better change your vote? At it is now, we cannot even create an
implementation proposal.
Hans
On 06/05/15 13:22, Jacopo Cappellato wrote:
On May 6, 2015, at 3:34 AM, Hans Bakker <h.bak...@antwebsystems.com> wrote:
It is no use, setting up an implementation plan when there is still a
possibility people will reject it.
Ok, if this was your goal then it seems you got your answer: most people are
inclined to Git (or will not object to it) but don't feel like it is actionable
enough for a vote now: defining an implementation plan, so that people can
understand how the actual every day work of the OFBiz community (committers,
contributors and users) with Git will be, would definitely help.
Jacopo
