Access to add and change pages is restricted. See: https://cwiki.apache.org/confluence/display/OFBIZ/Wiki+access

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 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.

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:

  • Combination of JIRA+Git is a success story within the ASF (lots of project using it for Project Mgt and providing insights to (potential) adopters and contributors
  • People knowing only Jira will need to adapt to GH workflow
  • JIRA is easier for non-development contributors to report and work with issues, and report on work open/done
  • Lack of project management dashboards and insights per current setup of the project.
  • Requires additional plugins [e.g. 4] to do stuff.
  • Other tools (JIRA/Confluence) must be kept for (much needed) history and slowly close old, inaccurate or deprecated tickets.

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.
  • No labels