Emmanuel Bourg wrote:
> I will check the latest version but I was under the impression bugzilla
> had a fine grained permission system. Private access is definitely
> supported by bugzilla, it's needed for security related bugs in Mozilla.
I don't see those in our version. I do see "bug groups",
Noel J. Bergman wrote:
Agreed. Jira and newer versions of bugzilla are similar in that sense,
although Jira's user-customizable dashboard seems to make better use of it.
Jira also has far more powerful permission schemes. The permission schemes
can be important. For example, it allows selective
Emmanuel Bourg wrote:
> JIRA just like Bugzilla doesn't support per component version numbers
Agreed. Jira and newer versions of bugzilla are similar in that sense,
although Jira's user-customizable dashboard seems to make better use of it.
Jira also has far more powerful permission schemes. Th
I've filed 2 requests in Bugzilla :
Bug 26098 - Upgrade to Bugzilla 2.16.x
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26098
Bug 26099 - Promote Jakarta Commons components to Bugzilla products
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26099
Emmanuel
Tim O'Brien wrote:
Emmanuel,
Th
Thank you Tim, but I'm not a committer unfortunately. I'll contact Pier
and offer my help but I don't expect to gain his trust easily.
Emmanuel Bourg
Tim O'Brien wrote:
Emmanuel,
Thanks for all of your help with release management for various commons
components, and taking the time to make su
Emmanuel,
Thanks for all of your help with release management for various commons
components, and taking the time to make sure that various sites are
maintained and updated. And now you've stepped up to the plate to
volunteer to upgrade our Bugzilla installation. If you are a committer,
join
> I agree with all of what you are saying, but all of these problems can be
> attacked with current technology and I am skeptical that adding new
> technology will make a huge difference. Of course I may be wrong.
Since the Directory project had long ago decided to use Jira, and was
waiting for it
Phil Steitz wrote:
What exactly does Jira have to do with release management and site
publishing? I am asking out of ignorance here. I thought Jira was an
issue tracker.
Issue tracking is central to cutting quality releases, and communicating
direction. Jira is more than issue tracking, IMO
Phil Steitz wrote:
What exactly does Jira have to do with release management and site
publishing? I am asking out of ignorance here. I thought Jira was an
issue tracker.
It *is* an issue tracker, so what it does very cleanly is associate bug
fixes with releases and provide a generated roadmap
Tim O'Brien wrote:
+1
What are the 4 or 5 pressing issues in Codec? Is anyone paying
attention to Latka lately? All we seem to have for collaboration is the
dev mailing list, we all get a weekly report of the open bugs from
Bugzilla, but does anyone ever bother to read that monstrosity? I th
Tim O'Brien wrote:
If you'd like to vote -1 on this product because someday, someone will
lament the lack of an OS issue tracker. I only ask you to focus on the
fact that there are a very few active committers who spend large amounts
of time regularly doing things like release management, site
11 matches
Mail list logo
