[llvm-dev] Adding new fields to bugzilla
Hans Wennborg via llvm-dev
llvm-dev at lists.llvm.org
Wed Jul 26 09:52:38 PDT 2017
I'm a little vary of adding more fields, because I think we already
have lots of fields that are never used.
Having said that, your suggestions seem reasonable, and it would be
cool if we could create tools to automate the release process a bit
more based on this.
On Mon, Jul 24, 2017 at 12:30 PM, Tom Stellard via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> On 07/04/2017 06:53 AM, Tom Stellard via llvm-dev wrote:
>> I would like to propose adding the following new fields/flags to bugzilla.
>> My goal is to make it easier to manage bug fixes and merges using automated
>> - "Trunk Revision(s)" field
>> This would give users a place to enter which revision(s) in trunk fixed a
>> particular bug. This would make it easy to generate a list of bugs fixed
>> by each release which could be included in the release notes.
>> - "Stable Revision(s)" field
>> This would give users a place to enter which revision(s) in the stable branch(es)
>> fixed a particular bug.
>> - "X.Y.Z Merge Request flags"
>> This is a flag you could set to request that the commits in the "Trunk Revision(s)"
>> field be merged into one of the stable branches. This along with the
>> "Trunk Revision" field would make it possible to nominate a bugfix for
>> a stable branch without having to create a new bug.
>> - "Code Owner Approval flag"
>> This flag you can set to show that code owner has approved merging the
>> "Trunk Revision(s)" commits to the requested branch.
>> - "Release Manager Approval flag"
>> This flag you can set to show that the release manager has approved merging the
>> "Trunk Revision(s)" commits to the requested branch
>> What do people think?
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
More information about the llvm-dev