You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 13
Next »
In dev ML at https://lists.apache.org/thread.html/r0e44a477ab39efa2b5d4c8816b67d381864a7bf60728d2915531e926%40%3Cdev.ofbiz.apache.org%3E we started a discussion about Pro and Cons with GH (GitHub) and Jira.
Positive aspects of Github+Git versus JIRA+Git
Github + Git | JIRA + Git |
---|
- Tight integration between Github and Git
- More known among developers
- Simple merge workflow (1 push button)
- Intrinsic tools available to version & release (git aspect)
- Enables developers in an easy way (forking/development collaborations)
| - More known in the enterprise world
- Success story for many projects of the ASF
- Lots of defined dashboards/overviews/etc. to provide insights to (potential) adopters and contributors
- Well defined integration between JIRA and Git
- Well defined separations of functions between JIRA and Git
- Project can define own fields/workflow (JIRA)
- Current setup of JIRA enables non-privileged contributors to participate in workflows (i.e take control to move forward, etc.)
|
Negative aspects of Github+Git versus JIRA+GIT
Github + Git | JIRA + Git |
---|
| - Loosely coupled integration between JIRA+GIT
|
References
- https://rocketmq.apache.org/docs/pull-request/
- https://issues.apache.org/jira/plugins/servlet/project-config/OFBIZ/administer-versions?status=released-unreleased
- https://help.github.com/en/github/managing-your-work-on-github/creating-an-issue
- "gren" is a small helpful robot that will do for you just create a release from a tag and compile the release notes using issues or commits.