Hi,
After reading through the mail every one has sent in, I have
come up with a revised set of rules. My comments are unindented.
manoj
1. In the first instance a package maintainer may decide
whethere a bug report not justified and close it if they
Christian Kurz wrote:
> Right, but the above sentence had in my opinion the intention that
> even QA-Members not have the permission so set a bug to priority fixed
> and this should be made clear. Also what should a QA-Member do if he
> finds a grave/important bug during freeze time and the maintai
Joey Hess <[EMAIL PROTECTED]> wrote:
> Christian Kurz wrote:
> > I'm not sure if this acceptable anymore as we are starting to revive
> > the qa-team. In some situationt they also need the right to close a bug
> > report and so we need to make the above statement clearer than now.
> The qa team is
[EMAIL PROTECTED] wrote:
> However I have had a bug or three closed by someone else -- for the wrong
> package. Most recently was an anacron bug that was closed by the ytalk maint.
> It was an accident, he fixed it the moment I told him, but it should not be
> possible to do.
>
> Now, perhaps a p
>
> Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> [A big part snipped as I agree to it.]
>
> > 4. Noone but the maintainer of a package (or someone acting on their
> > request) should close its bug reports.
>
> I'm not sure if this acceptable anymore as we are starting to revive
> the qa-team. I
Christian Kurz wrote:
> I'm not sure if this acceptable anymore as we are starting to revive
> the qa-team. In some situationt they also need the right to close a bug
> report and so we need to make the above statement clearer than now.
The qa team is either working on a package owned by debian-qa
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
[A big part snipped as I agree to it.]
> 4. Noone but the maintainer of a package (or someone acting on their
> request) should close its bug reports.
I'm not sure if this acceptable anymore as we are starting to revive
the qa-team. In some situationt t
On Tue, Jun 01, 1999 at 12:41:41PM -0500, Manoj Srivastava wrote:
> Hi,
>
> More than a year ago, Ian posted these rules governing
> disputes about bug reports. I found these acceptable, though I am
> somewhat leery of making thse _policy_. I would be happier if these
> were put togeth
Hi,
More than a year ago, Ian posted these rules governing
disputes about bug reports. I found these acceptable, though I am
somewhat leery of making thse _policy_. I would be happier if these
were put together in a document which is, like the developers
reference, a document meant to
On 11 Apr 1998, Adam P. Harris wrote:
> I see four possible valid parties for closing bugs:
> * party is the maintainer
> * party is the submitter
> * party has been given permission by the maintainer to close the bug
> (i.e., the maintainer is soliciting support from another developer
>
[EMAIL PROTECTED] writes:
> On Tue, Apr 07, 1998 at 10:39:42PM +0100, James Troup wrote:
> > and ask the maintainer to close them, but the maintainer should be
> > the one closing bugs, not some random individual on a clean up
> > crusade.
>
> I think this is an issue where it is difficult to lay
-BEGIN PGP SIGNED MESSAGE-
Manoj Srivastava wrote:
> In the specific dispute you are involved in, the letter of
> this proposed policy has already been followed.
In short, I would summarize my old bug as follows:
1) A .m file in the future (or a computer in the past) causes octave
-BEGIN PGP SIGNED MESSAGE-
Manoj is right. Rewording:
Are there any objections to the policy proposed by Ian?
I would like to see approved (by the usual procedures) a policy with
respect to bug reports as soon as possible, because we have no policy at
all so far (only "current practice")
Hi,
>>"Santiago" == Santiago Vila <[EMAIL PROTECTED]> writes:
Santiago> Could we please make this policy right now and fine-tune it
Santiago> later?
I strongly object to any such sentiment on general
principles. Something as important as policy should never be entered
into rashly, and
-BEGIN PGP SIGNED MESSAGE-
On Tue, 7 Apr 1998, Ian Jackson wrote:
> I also propose the following guidelines for determining whether a bug
> report should be kept open, etc. These may be stated elsewhere
> already, but should be consolidated:
>
> [snipped]
I mostly agree.
Could we pleas
> 4. Noone but the maintainer of a package (or someone acting on their
> request) should close its bug reports.
Why not the submitter himself?
Roman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, Apr 07, 1998 at 10:39:42PM +0100, James Troup wrote:
> Joost Kooij <[EMAIL PROTECTED]> writes:
> > I think it would be wiser to leave open the possibility for people to
> > browse the BTS and wield out obsoleted- and non-bugs, even if this
> > doesn't seem to happen very regularly at this m
>On Tue, 7 Apr 1998, Ian Jackson wrote:
>
>> 4. Noone but the maintainer of a package (or someone acting on their
>> request) should close its bug reports.
>
>We could be flexible here, in some cases:
>
>For example, if someone submits a bug, and just after sending the message
>he founds that it is
Joost Kooij <[EMAIL PROTECTED]> writes:
> On Tue, 7 Apr 1998, Ian Jackson wrote:
>
> > I propose the following rules for dealing with disputes over bug
> > reports:
>
> [snip]
>
> > 4. Noone but the maintainer of a package (or someone acting on
> > their request) should close its bug reports.
>
-BEGIN PGP SIGNED MESSAGE-
On Tue, 7 Apr 1998, Ian Jackson wrote:
> 4. Noone but the maintainer of a package (or someone acting on their
> request) should close its bug reports.
We could be flexible here, in some cases:
For example, if someone submits a bug, and just after sending the m
On Tue, 7 Apr 1998, Ian Jackson wrote:
> I propose the following rules for dealing with disputes over bug
> reports:
[snip]
> 4. Noone but the maintainer of a package (or someone acting on their
> request) should close its bug reports.
I assume that this applies primarily to cases where there i
I propose the following rules for dealing with disputes over bug
reports:
1. In the first instance a package maintainer may decide whethere a
bug report not justified and close it if they feel it isn't.
2. If the submitter (or anyone else) disagrees they should try to
resolve it by email with the
22 matches
Mail list logo
