Versions Compared

Old Version 5

changes.mady.by.user Pierre Smits

Saved on

compared with

New Version 6

changes.mady.by.user Pierre Smits

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Restructured page

]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.

Here they are for adopting the GH workflow by default:

Pro:

  • More devs know GH than Jira and it has been created for them (when using Git). They like it, we need them.
  • Simple things are easy to directly push with the PR commit button (w/ forced rebase and merge). For large or complicate other paths are possible, like attaching a patch. 
  • If we use both solutions we complicate things (mental overload, cf. the contributor wiki page). GH is an opportunity to simplify the processes.  Too much details[0] (bikeshedding) often does not help, KISS often helps.
  • Jacopo referred to an example of success (since 2016) in the GH wiki page[1].
  • As Infra team supports the dual-host it's not a venture
  • GH has intrinsically tools to version and release (it's a dev tool not a reporting tool).
  • Ability to create fork easily and work with peers on large or complicated subjects

Cons:

...


Positive aspects of Github+Git versus JIRA+Git

Github+GitJIRA+ 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)

Negative aspects of Git+Git versus JIRA+GIT

Github+GitJIRA+ Git
  • Less suited for project management reported (lack of dashboards etc per current setup of the report

  • INFRA is required for every workflow change to GITHUB

  • requires additional plugins to do stuff (ref #4)
  • Legacy tools need to be kept (for history sake, etc.)
  • Loosely coupled integration between JIRA+GIT

...


References

  1. https://rocketmq.apache.org/docs/pull-request/
  2. https://issues.apache.org/jira/plugins/servlet/project-config/OFBIZ/administer-versions?status=released-unreleased
  3. https://help.github.com/en/github/managing-your-work-on-github/creating-an-issue
  4. "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.