Maybe you could append a "Fixes: #xxxxx" to the commit message (similar to the Signed-of-by lines that are used in the linux kernel), then have an hook in the "official" repo close the ticket. This way the ticket is automatically closed iff and when the fix is merged to the official development branch.
Best, Gonzalo On Thu, Dec 19, 2013 at 10:01 AM, Volker Braun <vbraun.n...@gmail.com>wrote: > On Thursday, December 19, 2013 11:42:23 AM UTC, Jeroen Demeyer wrote: >> >> You could consider closing a ticket only *after* testing it on the >> buildbot (that was what I did) when it is as good as certain that it >> will actually be merged. > > > Yes, I've been doing both depending on how probable it seemed that the > ticket can break something. Still trying to get a feel for the best > workflow.... > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
