grim at reaperworld.com
Mon Oct 2 01:28:52 EDT 2017
On Mon, Oct 2, 2017 at 12:07 AM, Gary Kramlich <grim at reaperworld.com> wrote:
> On Sun, Oct 1, 2017 at 8:34 PM, Gary Kramlich <grim at reaperworld.com> wrote:
>> On Sep 29, 2017 03:10, "Robert Vehse" <robertvehse at fastmail.fm> wrote:
>> - Currently, tickets fixed by changes made to the 2.x.y branch are being
>> assigned the (non-existing) 2.10.13 milestone instead of 2.12.1.(See
>> https://developer.pidgin.im/ticket/16680#comment:5 for an example.) Is there
>> anyone willing and able to correct that?
>> I can take care of it unless someone wants to beat me to it.
> I took care of this. Forgot to do some steps in the giant script
> knows as the release process...
>> - Currently, newly created tickets are given the 2.12.1 milestone instead of
>> none at all. Is there anyone willing and able to correct that?
>> Guess I'll get this one too.
> I have no idea what's going on here. It looks like it's just using
> the default milestone, which makes sense.. but I don't know how to set
> a non default milestone once one is set. Maybe by changing it in the
> database directly, but I didn't want to attempt that in case someone
> actually knows how to do it.
dx found the solution, manually edit trac.ini :)
> Gary Kramlich <grim at reaperworld.com>
Gary Kramlich <grim at reaperworld.com>
More information about the Devel