<br><br>On Sunday, April 29, 2012, Christopher Schmidt wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Since the switch to Github, it appears that the OpenLayers project<br>
now uses two different mechanisms to manage incoming issues and<br>
tickets: Trac and Github issues.<br>
<br>
Right now, the project appears to have a number of pages directing<br>
new users to file tickets in trac, such as:<br>
<br>
<a href="http://trac.osgeo.org/openlayers/wiki/FilingTickets" target="_blank">http://trac.osgeo.org/openlayers/wiki/FilingTickets</a><br>
<a href="http://trac.osgeo.org/openlayers/wiki/FrequentlyAskedQuestions#SVN" target="_blank">http://trac.osgeo.org/openlayers/wiki/FrequentlyAskedQuestions#SVN</a><br>
<a href="http://trac.openlayers.org/" target="_blank">http://trac.openlayers.org/</a> being linked as 'support and development'<br>
from the homepage.<br>
<br>
It appears that new tickets are being created by users in trac at a<br>
rate of about 2 per week -- 20 issues created in the past 8 weeks, and<br>
741 open tickets, 43 awaiting review.<br>
<br>
In github, there are 109 open issues. Approximately 10 new issues are<br>
being created per week (40 in the last 18 days). The only obvious<br>
reference to Github anywhere in the OpenLayers project is a single 'Fork<br>
us on GitHub' link. (There are a couple other links in the trac wiki,<br>
but they're hidden relatively well, compared to the 'how to file a bug',<br>
and don't make it clear that tickets should be filed on github.)<br>
<br>
It looks like the question of where tickets should be made has been<br>
asked before on the mailing list, with no answer:<br>
<br>
<a href="http://lists.osgeo.org/pipermail/openlayers-dev/2012-January/008345.html" target="_blank">http://lists.osgeo.org/pipermail/openlayers-dev/2012-January/008345.html</a><br>
<br>
It was also informally discussed prior to that:<br>
<a href="http://lists.osgeo.org/pipermail/openlayers-dev/2011-October/008137.html" target="_blank">http://lists.osgeo.org/pipermail/openlayers-dev/2011-October/008137.html</a><br>
<br>
but it isn't obvious that any decision was made from that discussion;<br>
I don't see any discussion of what actions would need to be taken<br>
in order to shift development to the Github issue tracker (like, for<br>
example, updating our webpage to direct people there instead of to trac<br>
when filing new issues).<br>
<br>
It seems that developers are now closing trac tickets as duplicates of<br>
unsolved Github issues:<br>
<br>
<a href="https://github.com/openlayers/openlayers/issues/392" target="_blank">https://github.com/openlayers/openlayers/issues/392</a><br>
<a href="http://trac.osgeo.org/openlayers/ticket/3649" target="_blank">http://trac.osgeo.org/openlayers/ticket/3649</a><br>
<br>
In the past, I might have requested a vote, but it seems like a vote is<br>
really not even a plausible approach to the question at this point:<br>
what's done is done. If developers can confirm that OpenLayers is<br>
intending all future development to take place using the Github issue<br>
tracker, and that the trac issue tracker is now a dead end, then it<br>
would probably be best for new developers if a plan could be developed<br>
to help migrate the existing trac system into Github, starting with<br>
migrating links for development moving to Github instead of Trac as the<br>
recommended source.<br>
<br>
I look forward to any feedback from the active developers on how<br>
development is intended to work :)</blockquote><div> </div><div><br></div><div>Thanks for bringing this up Chris.</div><div><br></div><div>I'm in favour of using one issue tracker only, and I was planning to raise the issue after 2.12 final is out.</div>
<div><br></div><div>I'd like to use GitHub only. In this way we can easily cross-refence between issues, pull requests, commit messages, and review comments. Tracking is so important!</div><div><br></div><div dir="ltr">
I was a bit hesitant when I started the release process, because our release procedure relied on ticket fields, such as “version”, that GitHub does not offer. GitHub issues just have a “milestone” and “tags”.</div><div dir="ltr">
<br></div><span class="Apple-style-span" style>Since then I've started rewriting the release procedure [*], and I now think we can get by with what GitHub offers.</span><div></div><div><div><span class="Apple-style-span" style><br>
</span></div><div><span class="Apple-style-span" style>Cheers,<br></span><div></div><div><span class="Apple-style-span" style><br></span><div dir="ltr">[*] <<a href="http://trac.osgeo.org/openlayers/wiki/Release/Procedure">http://trac.osgeo.org/openlayers/wiki/Release/Procedure</a>></div>
</div></div></div><br><br>-- <br>Eric Lemoine<br><br>Camptocamp France SAS<br>Savoie Technolac, BP 352<br>73377 Le Bourget du Lac, Cedex<br><br>Tel : 00 33 4 79 44 44 96<br>Mail : <a href="mailto:eric.lemoine@camptocamp.com">eric.lemoine@camptocamp.com</a><br>
<a href="http://www.camptocamp.com">http://www.camptocamp.com</a><br><br>