I've been using my own testcase template to reproduce C#/.NET interop scenarios. It may be a good idea to include a similar thing in the docs to try and standardize the testcase code that devs receive.<br><br>Richard<br>
<br><div class="gmail_quote">On Mon, Feb 7, 2011 at 9:03 AM, Jeff Hardy <span dir="ltr"><<a href="mailto:jdhardy@gmail.com">jdhardy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I want to make sure I'm on the same page as everyone else when it<br>
comes to issue workflow. What I've been doing is:<br>
* For old bugs that aren't reproducible, just close it.<br>
* For old bugs that are reproducible, add test case and set "Release" to 2.7.<br>
* When fixing bugs, mark as "Fixed", make sure the release is set to<br>
the next release, and include the changeset hash in a comment.<br>
* On a release, close all "Fixed" bugs.<br>
<br>
All new bugs/CPython incompitibilities should have their "Release" set<br>
to 2.7 once they're confirmed; features should set to "3k" or<br>
"Future". I doubt all of those will get fixed for 2.7 and still have<br>
2.7 be released this year.<br>
<br>
I'm not sure what to do about bugs targeting 2.6.2; I would wager they<br>
could be re-targeted to 2.7.<br>
<br>
Any other suggestions on policy for the issue tracker? I want to get<br>
this written up before the weekend so that there are docs to point any<br>
new people at.<br>
<br>
- Jeff<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.ironpython.com">Users@lists.ironpython.com</a><br>
<a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" target="_blank">http://lists.ironpython.com/listinfo.cgi/users-ironpython.com</a><br>
</blockquote></div><br>