On 11 Mar 2016, at 20:58, Andrej Podhradsky wrote:
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,We rarely put affects version, fix version should be easy since the tests are updated
for a specific release of the projects/products.If not - it sounds like you are doing things that aren't even used which I know is not true.
Just looking at the issue list on https://github.com/jbosstools/jbosstools-integration-stack-tests/issues most
relates directly to Jira's.they even are not related to any of our product.
I don't grok this - any test is related to some of our projects (and thus eventually product).
From such issues tracked in github it is easy to create the appropriate
pull request.I don't grok what that means. It is trivial to create a pull request for jira's too - you just
refer to the jira in your commit and when opening pull-request it is automatically wired up and linked
to the jira issue.currently none of this is visible anywhere outside QE testing which I find a shame.
So, I see lots of advantages of doing it this way. Do you have any concerns
about this?My main concern it spreads overhead and maintenance of what is going on.
The fact that noone in dev seemed aware this useful tracking and extra work on the tests was going
on indicate to me the big issue of spreading our tracking of issues across multiple issue trackers.If you were commenting on the actual related jiras and opened specific test suite bugs in the relevant projects
your work would be much more visible and understood better - heck, it might be improved because dev would
notice you guys constantly have to keep adjusting things.tests is as much part of our development as the unit tests and runtime code is - it should be linked to
the issues it is done for IMO.That are my concerns.
Can't we find a better less segregated way for this ?
/max
Andrej
On Mar 11, 2016 6:13 PM, "Max Rydahl Andersen" manderse@redhat.com wrote: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/max
http://about.me/maxandersen
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev