Re: Standardizing the "latest dev code" Version field value in GNOME Bugzilla?

On Mon, 2015-01-12 at 16:43 -0600, Michael Catanzaro wrote:
On Mon, Jan 12, 2015 at 2:28 PM, Andre Klapper <ak-47 gmx net> wrote:
1) Does this variety of names create a real problem? For example,
does it make using git-bz harder (remembering the version value,
assuming you mostly develop against the latest code)? Do you care /
do enough people use git-bz / do people not use git-bz because of
this? Other reasons?

It's a minor annoyance to have to load Bugzilla in a web browser to
figure out the version to use when filing a bug with git-bz.

Agreed. I would actually call it a major annoyance, since it entirely
breaks the git-bz workflow. I think I'm just being an old man though.

Note that as long as there is also no standardized
General/general/Miscellaneous/misc component for all products, that
would still need to be done anyway to figure out what Component to use
when filing bugs with git-bz.

Actually, the components in a product can be queried using Bugzilla's
XMLRPC API, and if hooked up to tab completion in git-bz, could be used
from the command line:

2) Shall we standardize this? (I volunteer to rename; "git master"
seems to be the most popular option.) Or is that a waste of time?

I think standardizing on 'git master' would be great. Thanks for



Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]