Moving issues system to github

[Joel Costigliola]

Hi,

Alex and I were struggling with Jira administration lately.

We were thinking of moving our issue system on github at least for new
issues.

WDYT ?

Joel

[Ansgar Konermann]

Hi there,

as long as we can have all issues (also the older ones) in *one*
tracker, I've no special bias. I dislike going to two or three different
sites to collect all issues for FEST, however (old Google Code issues,
JIRA issues on Codehaus, new issues on github).

Are there any particular problems with the JIRA software itself? I think
JIRA is quite capable as an issue tracker, so I cannot really understand
the need to move. A few more details would be greatly appreciated. If it
is a permission issue, I think codehaus' staff can sort them out quickly.

Best regards

Ansgar

[Joel Costigliola]

Hi Ansgar,

I understand your point of not having doubles issue systems and I agree with that.

I personally find Jira ok (although I think it could have a better git integration) but Alex was unable to give me the rights to create versions, I don't have the details but it seemed complicated.

I'm ok to stay on Jira but we must fix this rights stuff, it's going to drive me crazy.

Cheers,

Joel

--
You received this message because you are subscribed to the Google Groups "easytesting-dev" group.
To post to this group, send email to easytes...@googlegroups.com.
To unsubscribe from this group, send email to easytesting-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/easytesting-dev?hl=en.

[Joel Costigliola]

Hi guys,

After discussing it with Alex, I now really think we should manage issues in github and no more in Jira.
The main reason being that some of our users have already created issues in github, so if we keep Jira we will have two issue trackers.
Github issues tracker is less rich than Jira but, IMHO, is sufficient for our needs (correct me if I'm wrong).
Moreover it will be better to have all in one place : code + issue tracker + doc.
It also much easier to create and update issue in github, not the case in Jira, for example once a user has created an issue in Jira he can't modify it ! too bad.
Last but not least, I can create milestones in github, I can't in JIra (not enough rights)

I think we should start by creating new issues in github and not in Jira and then move progressively the existing jira issues to github.
We would also have to communicate on that to our users.

Cheers,

Joel

To post to this group, send email to easytesting-dev@googlegroups.com.
To unsubscribe from this group, send email to easytesting-dev+unsubscribe@googlegroups.com.

[Ansgar Konermann]

Ok let's do it.

To view this discussion on the web visit https://groups.google.com/d/msg/easytesting-dev/-/1V124cfu4AcJ.
To post to this group, send email to easytes...@googlegroups.com.
To unsubscribe from this group, send email to easytesting-d...@googlegroups.com.

[Joel Costigliola]

Cool :)

Alex  could you mention in Fest Jira "home page" that issues must be created on github and make it read only ?

Thanks !

Joel

On Saturday, April 28, 2012 9:48:38 AM UTC+2, Ansgar Konermann wrote:

Ok let's do it.