The inherent challenge here is that everything reported against a git
version eventually turns into a report against a specific released
version once that version gets released. Ideally all such bug reports
would have the version number changed accordingly to the appropriate
number once the release is made. But that sounds really challenging to do.
In the absence of that, maybe just "git stable branch" and "git master
branch"?
Nate
On 6/15/23 09:14, Jack wrote:
I'll also ask what to do for reporting against head of a git branch
other than master? For programs that have a release or stable branch
(often named for the release number) there is a big difference between
head of that branch and git master. For example, KMyMoney has 5.1
branch. Unfortunately, I don't know if there is any way for this naming
to be consistent across applications and frameworks and .... unless
something like "git production branch."
Thoughts?
On 6/15/23 09:26, Nate Graham wrote:
My preference would be for "git master" but I'll gladly go with any
alternative consensus. What I think matters more is to get *something*
standardized.
Nate
On 6/15/23 00:52, Heiko Becker wrote:
On 6/14/23 20:15, Justin Zobel wrote:
I asked Nate but he said versions on Bugzilla are added by a script.
Can you please add git-master as a version for kio-extras on Bugzilla
on your next batch of updates, thank you.
On Thursday, 15 June 2023 04:17:09 CEST, Nate Graham wrote:
...And while we're doing this, maybe we can coordinate on a
consistent name for it. I see we use "master", "git master" and
"git-master" in various different places.
While it's true that a script is used to add Gear versions to
Bugzilla, it reads those versions from CMake's project(). So it'll
not be useful without a bit of hacking, once we decide on a
consistent name.
Regards,
Heiko
