If you want help moving them over give me a shout.<br><br><div class="gmail_quote">On Nov 18, 2007 5:34 PM, David Chelimsky <<a href="mailto:dchelimsky@gmail.com">dchelimsky@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Nov 18, 2007 3:16 PM, David Chelimsky <<a href="mailto:dchelimsky@gmail.com">dchelimsky@gmail.com</a>> wrote:<br>> Hi everybody.<br>><br>> Per <a href="http://rubyforge.org/pipermail/rspec-users/2007-November/004572.html" target="_blank">
http://rubyforge.org/pipermail/rspec-users/2007-November/004572.html</a>,<br>> we're going to be moving ticket tracking over to lighthouse. We'd like<br>> to get this rolling sooner than later, but we're fairly well occupied
<br>> getting ready for the 1.1 release and writing rspec books :)<br>><br>> We've got the lighthouse account set up. The thing we need to do to<br>> start using it is to get all the open tickets at rubyforge copied over
<br>> to lighthouse. As of today, lighthouse does not offer any sort of<br>> automated means of doing that.<br>><br>> If any of you are interested in helping out by either manually copying<br>> tickets over or devising an automated means of doing so, please speak
<br>> up. It would be a big help to the both the rspec community and the<br>> rspec development team.<br><br></div>A few people have offered on the two different lists (rspec-users and<br>rspec-devel), so it looks like this might happen sooner than later.
<br><br>Some ground rules:<br><br>We need to get all of the open tickets at rubyforge in all three<br>trackers: bugs, patches and feature requests. Right now there are 123<br>in total.<br><br>There is only one tracker at lighthouse, and tickets are grouped via
<br>tags. So tickets that come from the bug tracker should be tagged<br>'bug'. From Feature Requests: 'featurerequest'. From Patches: 'patch'.<br>Simple?<br><br>The LH ticket should either include all of the commentary from the RF
<br>ticket or at least a link back to the old ticket for reference.<br><br>Do not worry about assigning responsibility. We will grab tickets that<br>we want to work on.<br><br>When they get moved over, they should get closed on rubyforge with a
<br>message saying "This ticket was moved to" with a link to the new<br>ticket.<br><br>I'll put up a notice on Rubyforge that we are moving to lighthouse and<br>new tickets should go there with a cutoff (i.e
. any ticket above 15719<br>on rubyforge will be ignored). I don't know yet if I can archive those<br>trackers. I'll look into that this week.<br><br>Questions?<br><br>Cheers,<br><font color="#888888">David<br></font>
<div><div></div><div class="Wj3C7c"><br>><br>> Cheers,<br>> David<br>><br>_______________________________________________<br>rspec-users mailing list<br><a href="mailto:rspec-users@rubyforge.org">rspec-users@rubyforge.org
</a><br><a href="http://rubyforge.org/mailman/listinfo/rspec-users" target="_blank">http://rubyforge.org/mailman/listinfo/rspec-users</a><br></div></div></blockquote></div><br>