>> As I understand it, it involves editing the mysql database by hand (well
>> by a script) instead of doing it inside bugzilla. Daniel Berlin has
>> done that the last couple of releases.
>
> I have checked in the attached patch to add this step to the branching
> checklist. I will now ask Daniel to help with the SQL bits.
Sorry, here's the patch.
So the way i actually do this is with a crappy perl script.
in /home/dberlin on sourceware.org, there is a script called 42changer.pl.
I just copy it to the next version number (43changer.pl in this case),
and edit the script to do so it changes 4.2 regression to 4.2/4.3
regression instead of changing (in this case) 4.1 regression to
4.1/4.2 regression.
I'm just saying this for posterity sake so if someone needs to lookup
how this actually gets done, they know :)
If i actually knew perl, i'm sure it would be trivial to just make
this stuff a command line parameter to the script.
But i'm afraid of perl, and afraid that if i tried, it would end up
only working on months that end in the letter r or something, since
that is perl for you.
Anyway, i made 43changer.pl and ran it, so the bug summaries have been updated.
