Hi,
any more opinions on this? I'd like to move forward with it, but not if
there isn't anybody else who thinks this would be interesting..
It's just that, with last push, between solving, closing and being a
watcher on some of the issues I've received ~20 e-mails that
won't go anywhere, as I also
Hi Juergen,
AIUI, issues in Jira would remain there forever, in read only mode,
whatever the issues' migration approach. We'd add some prominent links on
README.md, home page, jira itself, etc. Existing links to Jira issues would
still remain reachable.
I asked at users@infra.a.o what path did Ai
The issues in Jira should not get lost, neither the closed ones. It is
important history.
A quick search finds some migration scripts:
https://stackoverflow.com/questions/31125655/is-there-a-way-to-import-jira-issues-to-github
https://gist.github.com/graemerocher/ee99ddef8d0e201f0615
and Spring
Hi,
some weeks ago, a thread on users@infra.a.o highlighted the benefits of
moving from jira to github issues, based on Apache Airflow
experience, which has been summarized here:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191332632
I've been mulling it since then and I've be
