Page History

...

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

...

Does GH have tools to version and release software?
Answer: Yes, it does: when you create a git tag, GitHub provides download links that allow the users to generate and download an archive of that tag.
Question: Can we modify our release process to leverage GH instead of what we are doing now?
Answer: No, accordingly to the ASF "Release Distribution" policy [*] we would still need to publish and distribute our releases in the current way;
of course we can also adopt other downstream channels.

...

)

...

.

...

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

We are not using Jira to manage releases. But when we publish a new release
we update Jira versions to reflect the change. This information is useful
to group Jira tickets by version. I am not sure if there is a similar
feature in GH.