Hey Max,
we use github tracker only for issues related to our tests. We found it much more flexible then using jira for isues such as "Improve stability of XYZTest". For such issues it is hard to specify affects version or fixed version, they even are not related to any of our product.
>From such issues tracked in github it is easy to create the appropriate pull request.
So, I see lots of advantages of doing it this way. Do you have any concerns about this?
Andrej
On 10 Mar 2016, at 19:29, Alexey Kazakov wrote:
Hi Jozef,
Sorry for not answering earlier. I'm on EclipseCon this week.
We didn't know that you are using github issues instead of JIRA.Yeah, that is a surprise for me too. We are not supposed to use issue tracker on any github repos for jbosstools.
Everything should be tracked in jira (JBIDE, JBDS, JBTIS etc.)
I guess I can add you to the needed github team but I'm ccing this to jbosstools-dev list to make sure we are doing it right. Max?
Len - any idea why we now are doing this ?
/max
On Mar 9, 2016, at 2:50 AM, Jozef Marko jomarko@redhat.com wrote:
Hello Alexey,
I am quite often contributing to the repository [1]. I have discussed with Andrej Podhradsky (apodhrad), that you are able to give me access to this repository.
Currently, the main problem is, that I can't be assigned as 'Assignee' for any issue in this repository.
Please let me know, if you are able to help me.
Thanks
Regards, Jozef.
[1]
https://github.com/jbosstools/jbosstools-integration-stack-tests
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev