I've finished the import of the issues from GitHub to JIRA. I would recommend to switch over to JIRA now.
On Wed, Jun 18, 2014 at 9:15 AM, Robert Metzger <[email protected]> wrote: > @Vladimir: Just to clarify, my tool is not an automated mirror that is > synchronizing changes between the two systems. Its a one-time tool to do an > initial import for the GitHub issues into JIRA. After that, we have to use > JIRA for Optiq. > > I think there is no way around using JIRA as a issue-tracker. > Our project is using the ASF-GitHub integration described here: > https://blogs.apache.org/infra/entry/improved_integration_between_apache_and > Other projects such as Spark or Mahout are also using that integration. > > It is a step into the right direction, because you can use the nice GitHub > pull request feature (including line-wise comments) in combination with > JIRA. > You'll have a GitHub mirror of your Apache Git repository like this: > https://github.com/apache/incubator-flink > All pull requests and comments trigger an email to the dev@ list. If the > pull request contains a JIRA id (like FLINK-123), the bot will add a > comment into the respective issue. > I would recommend using that setup. > > I have no experience regarding Review board. But it seems that every > developer has to install the "rbt" tool. > I'm trying to do the import into JIRA today. > > > > On Wed, Jun 18, 2014 at 4:10 AM, Julian Hyde <[email protected]> wrote: > >> On Jun 17, 2014, at 10:35 AM, Vladimir Sitnikov < >> [email protected]> wrote: >> >> > Is there a way to connect JIRA to the repository so it can show the >> actual >> > changes applied to the repository? >> > >> > Is there a way to add a comment to a particular line? In github you just >> > point-and-click. >> >> I don’t know all the details yet. But I do know that the Drill team tried >> to continue using the github process and needed to pull back, somewhat, to >> fit within the Apache process. For instance, they require patches >> physically attached to jira cases (the patches might have been generated >> from pull requests, but the process is jira+patches). >> >> If they tried, and failed, to work in the "github way" then we shouldn’t >> try too hard. We’d blunt our swords when there are more important dragons >> to slay (the join combinatorics beast springs to mind). I’ve noticed that >> Apache infrastructure are continually making improvements to allow “modern” >> forms of development, so things will get easier over time. >> >> Apache supports Review board (see e.g. how Hive use it [1]). If we >> choose, we can use review board also. >> >> Julian >> >> [1] https://cwiki.apache.org/confluence/display/Hive/Review+Board >> >> >
