Re: [sage-devel] Re: Do not close tickets
On Mon, Jul 12, 2010 at 3:15 AM, Simon King simon.k...@nuigalway.ie wrote: What does closing a ticket mean? Is it the same as providing a resolution such as fixed, wontfix, duplicate? Or is closing the ticket something that comes *after* providing a resolution? I think for clear cut cases, it's reasonable for people to close tickets as duplicate (e.g. if they filed a ticket, then noticed that someone else did the same--close the earlier one or the one with the least work on it). Fixed usually requires at least a regression test patch, and wontfix shouldn't be taken lightly. The main issue is people closing tickets that should have had some action involved, anyone but the release manager closing things is just asking for trouble. - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Do not close tickets
Hi Robert, On 12 Jul., 12:27, Robert Miller r...@rlmiller.org wrote: If providing resolution and closing is the same, then I recently closed a ticket out of ignorance. They are indeed the same. Which ticket was it? #2151. I am sorry for that. At least, there is no code attached to that ticket, and actually nobody had a good idea how to (doc)test the problem once it is fixed. But it is fixed now (and I have no idea who did it...). Cheers, Simon -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Do not close tickets
I am sorry for that. Don't be! Just to be perfectly clear, I'm not trying to be totalitarian here. I think the following is a good rule of thumb: If there is anything on the ticket that needs to be merged, even if it is part of another ticket or implied by another ticket, or there is anyone around who thinks the ticket should not be closed, contact your local release manager instead of closing it yourself. Also, some release managers might want credit for closing an irrelevant ticket during their release (I don't care but some might). -- Robert L. Miller http://www.rlmiller.org/ -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Do not close tickets
On 2010-Jul-12 12:27:57 +0200, Robert Miller r...@rlmiller.org wrote: On Mon, Jul 12, 2010 at 12:15 PM, Simon King simon.k...@nuigalway.ie wrote: If providing resolution and closing is the same, then I recently closed a ticket out of ignorance. They are indeed the same. Which ticket was it? Likewise, I just did the same to #5864 (though it's not clear that my choice is correct since there is no obvious withdraw or no longer relevant option). My apologies but I had only read the beginning of this thread. I did check that the next state was resolved (which I am used to being a different state to closed). -- Peter Jeremy pgp8UTFQkqXRr.pgp Description: PGP signature
[sage-devel] Re: Do not close tickets
Hi Robert and William, What does closing a ticket mean? Is it the same as providing a resolution such as fixed, wontfix, duplicate? Or is closing the ticket something that comes *after* providing a resolution? If providing resolution and closing is the same, then I recently closed a ticket out of ignorance. Cheers, Simon -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Do not close tickets
On Mon, Jul 12, 2010 at 12:15 PM, Simon King simon.k...@nuigalway.ie wrote: Hi Robert and William, What does closing a ticket mean? Is it the same as providing a resolution such as fixed, wontfix, duplicate? Or is closing the ticket something that comes *after* providing a resolution? If providing resolution and closing is the same, then I recently closed a ticket out of ignorance. They are indeed the same. Which ticket was it? Cheers, Simon -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -- Robert L. Miller http://www.rlmiller.org/ -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Do not close tickets
This would be a good reason for us to setup a separate trac server for the notebook. It's tempting. There's probably also a way to make it so http://trac.sagemath.org/sage_notebook is a trac just for the notebook. However, at the very least one would want to have intense integration between this and Sage's trac. What if something at this new Trac needed to include a Sage library patch that affected someone who doesn't develop on the notebook? Also, I see the potential for even more balkanization when it comes to the notebook. - kcrisman -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Do not close tickets
On Jul 12, 12:59 pm, William Stein wst...@gmail.com wrote: On Monday, July 12, 2010, kcrisman kcris...@gmail.com wrote: This would be a good reason for us to setup a separate trac server for the notebook. It's tempting. There's probably also a way to make it so http://trac.sagemath.org/sage_notebook is a trac just for the notebook. However, at the very least one would want to have intense integration between this and Sage's trac. What if something at this new Trac needed to include a Sage library patch that affected someone who doesn't develop on the notebook? Also, I see the potential for even more balkanization when it comes to the notebook. Separating the notebook from sage is by far the best chance we have to reduce the number of different competing notebook projects. The less tight the integration with sage the better for this True, but that doesn't address the problem of how to deal with sagenb patches that require complementary sage library patches, especially for non-notebook developers who would find it difficult to wait several months for a new spkg if there was something they needed (don't ask me for a specific example, I'm just raising a hypothetical here). - kcrisman -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
