Christopher Faylor cgf-use-the-mailinglist-ple...@cygwin.com writes:
Can I get a show of hands? How many package maintainers would like to
have a bug tracker?
There is only one good, easy to use, user/maintainer friendly bug
tracker I know of:
debbugs [1]
The best thing about
On Wed, Aug 25, 2010 at 05:06:42PM +0300, Jari Aalto wrote:
Christopher Faylor cgf-use-the-mailinglist-ple...@cygwin.com writes:
Can I get a show of hands? How many package maintainers would like to
have a bug tracker?
There is only one good, easy to use, user/maintainer friendly bug
tracker
On 20/08/2010 19:01, Christopher Faylor wrote:
Can I get a show of hands? How many package maintainers would like to
have a bug tracker?
I would definitely use it, the same way I currently use the GCC bug tracker:
I'd set up a whine email reminder, so that I didn't have to exert any extra
Can I get a show of hands? How many package maintainers would like to
have a bug tracker?
One problem that I see immediately is that if we publicly adopt a bug
tracker EVERY maintainer will have to use it. We can't expect a normal
user to understand that they send email to the mailing list
2010/8/20 Christopher Faylor cgf-use-the-mailinglist-ple...@cygwin.com:
Can I get a show of hands? How many package maintainers would like to
have a bug tracker?
1+
Yes, it's a lot more work for all parties, the server maintainer,
the package maintainer and the user. And I believe
On 8/20/2010 11:01 AM, Christopher Faylor wrote:
Can I get a show of hands? How many package maintainers would like to
have a bug tracker?
-0 (Not in favor, but I'll monitor it if it's implemented.)
We're still going to have to monitor the mailing list, so this just adds
burden AFAICT. Does
On Fri, Aug 20, 2010 at 08:11:31PM +0200, Reini Urban wrote:
2010/8/20 Christopher Faylor cgf-use-the-mailinglist-ple...@cygwin.com:
Can I get a show of hands? ?How many package maintainers would like to
have a bug tracker?
1+
Yes, it's a lot more work for all parties, the server maintainer
On Fri, Aug 20, 2010 at 11:22:46AM -0700, David Rothenberger wrote:
On 8/20/2010 11:01 AM, Christopher Faylor wrote:
Can I get a show of hands? How many package maintainers would like to
have a bug tracker?
-0 (Not in favor, but I'll monitor it if it's implemented.)
We're still going to have
On Fri, Aug 20, 2010 at 02:24:31PM -0400, Christopher Faylor wrote:
On Fri, Aug 20, 2010 at 08:11:31PM +0200, Reini Urban wrote:
2010/8/20 Christopher Faylor cgf-use-the-mailinglist-ple...@cygwin.com:
Can I get a show of hands? ?How many package maintainers would like to
have a bug tracker?
1
On Aug 20 14:31, Christopher Faylor wrote:
On Fri, Aug 20, 2010 at 11:22:46AM -0700, David Rothenberger wrote:
On 8/20/2010 11:01 AM, Christopher Faylor wrote:
Can I get a show of hands? How many package maintainers would like to
have a bug tracker?
-0 (Not in favor, but I'll monitor
On Fri, 2010-08-20 at 14:01 -0400, Christopher Faylor wrote:
Can I get a show of hands? How many package maintainers would like to
have a bug tracker?
Depends on how we use it.
Don't get me wrong -- I like working with Bugzilla, and we do use it
*internally* for Cygwin/X, but the list
On Fri, 2010-08-20 at 13:51 -0500, Yaakov (Cygwin/X) wrote:
OTOH, I do sometimes miss things on the main list due to the
signal-to-noise ratio, which I imaging would be even greater for a
maintainer with only a small number of packages. So using Bugzilla
internally would be helpful.
IOW:
On 19.08.2010 23:11, Eric Blake wrote:
On 08/19/2010 01:59 PM, Jeremy Bopp wrote:
Of course the quality of the defect tracker is directly related to the
effort the maintainers put in to keep it relatively pruned and
organized. Maybe that is too much to expect for most maintainers at
this time.
nudging.
Agreed, but OTOH I'd guess that half of all of the bugs reported on this
list are for just two packages: cygwin and setup.exe. If the maintainers
of those two packages think a bug tracker would be useful, we should make
one. If they don't, it's probably not worth bothering.
setup
to any
mail about their package, or who only reply after some nudging.
Agreed, but OTOH I'd guess that half of all of the bugs reported on this
list are for just two packages: cygwin and setup.exe. ?If the maintainers
of those two packages think a bug tracker would be useful, we should make
one
could set up my own bug tracker, and that this might actually be useful
to the project.
To be sure, I had wondered if I could set up such a system and include a
moderate amount of advertising on the site and that this might prove to
be a moderately profitable activity.
But, having a sniff
It might be helpful if I could be clear what the reasons for not having
a bug tracker are.
I could take a stab as:
1. It is not the feeling of the Cygwin maintainers that a bug tracker
would provide a significantly better solution than the current mailing
list solution
2
On 19/08/2010 14:57, Andrew Schulman wrote:
I think that a bug tracker would be a nice improvement to our
development workflow. As a package maintainer, I'd love to be able to
call up a page of all of the open bugs for all of the packages I maintain.
I also think that the work to set up
On Aug 19 09:57, Andrew Schulman wrote:
It might be helpful if I could be clear what the reasons for not having
a bug tracker are.
I could take a stab as:
1. It is not the feeling of the Cygwin maintainers that a bug tracker
would provide a significantly better solution than
I'd guess that half of all of the bugs reported on this
list are for just two packages: cygwin and setup.exe. If the maintainers
of those two packages think a bug tracker would be useful, we should make
one. If they don't, it's probably not worth bothering.
Somebody would have to set up
reply after some nudging.
Agreed, but OTOH I'd guess that half of all of the bugs reported on this
list are for just two packages: cygwin and setup.exe. If the maintainers
of those two packages think a bug tracker would be useful, we should make
one. If they don't, it's probably not worth
http://cygwin.com/acronyms/#SHTDI ?
Auto-updating the package categories daily doesn't seem hard to me, I would
build that if we had a bug tracker working.
But before we get to that point, I'd have a few other questions.
(1) Most important: How many people care? Do users want a bug tracker
What is the status of http://cygwin.com/bugzilla? It appears to have been
in use at least last year.
Provisional effort? Occasionally used? Useful, not useful?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On 8/19/2010 10:18 AM, Andrew Schulman wrote:
(1) Most important: How many people care? Do users want a bug tracker?
Would package maintainers use it? Would the cygwin and setup.exe
maintainers use it?
Andrew Schulman and Bill Blunn would find a bug tracker useful, but that's
not enough
On Aug 19 11:23, Andrew Schulman wrote:
What is the status of http://cygwin.com/bugzilla? It appears to have been
in use at least last year.
Provisional effort? Occasionally used? Useful, not useful?
Not used for Cygwin, right now.
Corinna
--
Corinna Vinschen Please,
On Aug 19 11:18, Andrew Schulman wrote:
http://cygwin.com/acronyms/#SHTDI ?
Auto-updating the package categories daily doesn't seem hard to me, I would
build that if we had a bug tracker working.
But before we get to that point, I'd have a few other questions.
(1) Most important
On Aug 19 11:23, Andrew Schulman wrote:
What is the status of http://cygwin.com/bugzilla? It appears to have been
in use at least last year.
Provisional effort? Occasionally used? Useful, not useful?
Not used for Cygwin, right now.
CGF was using it at least a little bit last year:
On Thu, Aug 19, 2010 at 11:18:48AM -0400, Andrew Schulman wrote:
http://cygwin.com/acronyms/#SHTDI ?
Auto-updating the package categories daily doesn't seem hard to me, I would
build that if we had a bug tracker working.
But before we get to that point, I'd have a few other questions.
(1) Most
On Thu, Aug 19, 2010 at 11:02:35AM -0500, Jeremy Bopp wrote:
On 8/19/2010 10:18 AM, Andrew Schulman wrote:
(1) Most important: How many people care? Do users want a bug tracker?
Would package maintainers use it? Would the cygwin and setup.exe
maintainers use it?
Andrew Schulman and Bill
On Thu, Aug 19, 2010 at 07:05:53PM +0200, Corinna Vinschen wrote:
On Aug 19 11:23, Andrew Schulman wrote:
What is the status of http://cygwin.com/bugzilla? It appears to have been
in use at least last year.
Provisional effort? Occasionally used? Useful, not useful?
Not used for Cygwin,
On Thu, Aug 19, 2010 at 01:26:03PM -0400, Andrew Schulman wrote:
On Aug 19 11:23, Andrew Schulman wrote:
What is the status of http://cygwin.com/bugzilla? It appears to have
been in use at least last year.
Provisional effort? Occasionally used? Useful, not useful?
Not used for Cygwin, right
to be expecting a bug
tracker will be used for technical support so that if someone is having
problems setting up openssh they will be walked through the problem in
the bug tracker. I'd actually expect that a user error would be closed
as user error. And, subsequent reports of the problem
On 08/19/2010 01:59 PM, Jeremy Bopp wrote:
Of course the quality of the defect tracker is directly related to the
effort the maintainers put in to keep it relatively pruned and
organized. Maybe that is too much to expect for most maintainers at
this time.
Bingo. That's why I'm perfectly
33 matches
Mail list logo
