<div class="markdown">
<p dir="auto">On 14 Mar 2016, at 9:55, Andrej Podhradsky wrote:</p>
<blockquote>
<p dir="auto">Hey Max, Alexey,</p>
<p dir="auto">first of all, could you grant the access to the repo to jomarko, please?<br>
(no matter which issue tracker we use he will need that permission).</p>
</blockquote>
<p dir="auto">He has been invited so once he accepts the invite he can push.</p>
<blockquote>
<p dir="auto">Regarding to our discussion of using github issue tracker:<br>
- affects and fixed versions are not so important if we do not make<br>
releases (we do not release tests)</p>
</blockquote>
<p dir="auto">I completely disagree with that. The tests are supposed to be done <em>before</em> we release<br>
some specific version is it not ? So it is as tied to a specific release, if not more.</p>
<blockquote>
<ul>
<li>it is comfortable to use the github tracker</li>
</ul>
</blockquote>
<p dir="auto">Sure, if you don't care about the rest of the team and being able to actually query<br>
and get an overview of how much is actually going on/blocking.</p>
<blockquote>
<ul>
<li>multiple issue trackers... well, we use github for other projects so this
doesn't add another tracker to our list of trackers (jira, bugzilla,
eclipse bugzilla, github, gitlab)</li>
</ul>
</blockquote>
<p dir="auto">if this was a completely different project I would buy that - it isn't ;)</p>
<blockquote>
<p dir="auto">But I agree with your argument that we are not seen. Let me think of it and<br>
probably we will go back to the jira.</p>
</blockquote>
<p dir="auto">Lets at least get whatever painpoints identified rather than just jump to github<br>
without any notification ;)</p>
<p dir="auto">/max</p>
<blockquote>
<p dir="auto">Best Regards</p>
<p dir="auto">Andrej</p>
<p dir="auto">On Sat, Mar 12, 2016 at 11:15 AM, Max Rydahl Andersen <a href="mailto:manderse@redhat.com">manderse@redhat.com</a><br>
wrote:</p>
<blockquote>
<p dir="auto">On 11 Mar 2016, at 20:58, Andrej Podhradsky wrote:</p>
<p dir="auto">Hey Max,</p>
<p dir="auto">we use github tracker only for issues related to our tests. We found it<br>
much more flexible then using jira for isues such as "Improve stability of<br>
XYZTest". For such issues it is hard to specify affects version or fixed<br>
version,</p>
<p dir="auto">We rarely put affects version, fix version should be easy since the tests<br>
are updated<br>
for a specific release of the projects/products.</p>
<p dir="auto">If not - it sounds like you are doing things that aren't even used which I<br>
know is not true.</p>
<p dir="auto">Just looking at the issue list on<br>
<a href="https://github.com/jbosstools/jbosstools-integration-stack-tests/issues">https://github.com/jbosstools/jbosstools-integration-stack-tests/issues</a><br>
most<br>
relates directly to Jira's.</p>
<p dir="auto">they even are not related to any of our product.</p>
<p dir="auto">I don't grok this - <em>any</em> test is related to <em>some</em> of our projects (and<br>
thus eventually product).</p>
<p dir="auto">From such issues tracked in github it is easy to create the appropriate<br>
pull request.</p>
<p dir="auto">I don't grok what that means. It is trivial to create a pull request for<br>
jira's too - you just<br>
refer to the jira in your commit and when opening pull-request it is<br>
automatically wired up and linked<br>
to the jira issue.</p>
<p dir="auto">currently none of this is visible anywhere outside QE testing which I find<br>
a shame.</p>
<p dir="auto">So, I see lots of advantages of doing it this way. Do you have any concerns<br>
about this?</p>
<p dir="auto">My main concern it spreads overhead and maintenance of what is going on.</p>
<p dir="auto">The fact that noone in dev seemed aware this useful tracking and extra<br>
work on the tests was going<br>
on indicate to me the big issue of spreading our tracking of issues across<br>
multiple issue trackers.</p>
<p dir="auto">If you were commenting on the actual related jiras and opened specific<br>
test suite bugs in the relevant projects<br>
your work would be much more visible and understood better - heck, it<br>
might be improved because dev would<br>
notice you guys constantly have to keep adjusting things.</p>
<p dir="auto">tests is as much part of our development as the unit tests and runtime<br>
code is - it should be linked to<br>
the issues it is done for IMO.</p>
<p dir="auto">That are my concerns.</p>
<p dir="auto">Can't we find a better less segregated way for this ?</p>
<p dir="auto">/max</p>
<p dir="auto">Andrej<br>
On Mar 11, 2016 6:13 PM, "Max Rydahl Andersen" <a href="mailto:manderse@redhat.com">manderse@redhat.com</a> wrote:</p>
<p dir="auto">On 10 Mar 2016, at 19:29, Alexey Kazakov wrote:</p>
<p dir="auto">Hi Jozef,</p>
<p dir="auto">Sorry for not answering earlier. I'm on EclipseCon this week.<br>
We didn't know that you are using github issues instead of JIRA.</p>
<p dir="auto">Yeah, that is a surprise for me too. We are <em>not</em> supposed to use issue<br>
tracker on any github repos for jbosstools.</p>
<p dir="auto">Everything should be tracked in jira (JBIDE, JBDS, JBTIS etc.)</p>
<p dir="auto">I guess I can add you to the needed github team but I'm ccing this to<br>
jbosstools-dev list to make sure we are doing it right. Max?</p>
<p dir="auto">Len - any idea why we now are doing this ?</p>
<p dir="auto">/max</p>
<p dir="auto">On Mar 9, 2016, at 2:50 AM, Jozef Marko <a href="mailto:jomarko@redhat.com">jomarko@redhat.com</a> wrote:</p>
<p dir="auto">Hello Alexey,</p>
<p dir="auto">I am quite often contributing to the repository [1]. I have discussed with<br>
Andrej Podhradsky (apodhrad), that you are able to give me access to this<br>
repository.</p>
<p dir="auto">Currently, the main problem is, that I can't be assigned as 'Assignee' for<br>
any issue in this repository.</p>
<p dir="auto">Please let me know, if you are able to help me.</p>
<p dir="auto">Thanks</p>
<p dir="auto">Regards, Jozef.</p>
<p dir="auto">[1]</p>
<h2><a href="https://github.com/jbosstools/jbosstools-integration-stack-tests">https://github.com/jbosstools/jbosstools-integration-stack-tests</a></h2>
<p dir="auto">jbosstools-dev mailing list<br>
<a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></p>
<p dir="auto">/max</p>
<h2><a href="http://about.me/maxandersen">http://about.me/maxandersen</a></h2>
<p dir="auto">jbosstools-dev mailing list<br>
<a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></p>
<p dir="auto">/max<br>
<a href="http://about.me/maxandersen">http://about.me/maxandersen</a></p>
</blockquote>
</blockquote>
<p dir="auto">/max<br>
<a href="http://about.me/maxandersen">http://about.me/maxandersen</a></p>
</div>