On Wed, Jan 21, 1998 at 03:59:03AM -0800, Guy Maor wrote:
> [EMAIL PROTECTED] (Richard Braakman) writes:
>
> > I think that any of these measures would be preferable to introducing
> > a new class of "fixed but open" bugs. Such bugs would interfere with
> > the attempts to use the bug system as a
[EMAIL PROTECTED] (Richard Braakman) writes:
> I think that any of these measures would be preferable to introducing
> a new class of "fixed but open" bugs. Such bugs would interfere with
> the attempts to use the bug system as an aid to release engineering,
I don't think that there are so many
Guy Maor wrote:
> [EMAIL PROTECTED] (Kai Henningsen) writes:
>
> > I thought we had agreed on
> >
> > * If the nmu fixes many bugs, close the bugs, but reopen a new one
> > with the diffs
>
> No, there's often times valuable information in the bug report. What
> if the non-maintainer rele
Gregor Hoffleit <[EMAIL PROTECTED]> writes:
> Regarding the notification about fixed bugs in nmu's: Is it really
> intentional that this way (what Christian and Guy propose) the fixed
> bugs won't be recorded anywhere in the package (since I can't list
> them in the changelog), but would onl
James Troup <[EMAIL PROTECTED]> wrote:
Gregor Hoffleit <[EMAIL PROTECTED]> writes:
> Guy wrote:
> > * If the nmu fixes many bugs, close the bugs, but reopen a new
> > one with the diffs
>
> This is a diff [ ... ]
Please watch your citations, Kai wrote that, not Guy. A
Gregor Hoffleit <[EMAIL PROTECTED]> writes:
> Guy wrote:
> > * If the nmu fixes many bugs, close the bugs, but reopen a new one
> > with the diffs
>
> This is a diff [ ... ]
Please watch your citations, Kai wrote that, not Guy. And FWIW I
agree with Guy, I do not like the idea of bugs being c
Guy wrote:
> * If the nmu fixes many bugs, close the bugs, but reopen a new one
> with the diffs
This is a diff between the last maintainer release and this nmu ? What about
nmu releases of new upstream versions ? I guess a diff between the last
maintained release and the nmu would make not mu
[EMAIL PROTECTED] (Kai Henningsen) writes:
> I thought we had agreed on
>
> * If the nmu fixes many bugs, close the bugs, but reopen a new one
> with the diffs
No, there's often times valuable information in the bug report. What
if the non-maintainer release doesn't correctly fix the bug?
[EMAIL PROTECTED] (Christian Schwarz) wrote on 13.01.98 in <[EMAIL PROTECTED]>:
>* (As current policy says) the person doing the non-maintainer upload
> should send a bug report to the bug tracking system explaining his/her
> changes. This is extremly important so that the usual mai
[This mail is part of Debian Policy Weekly issue #5]
Topic 2: Maintainer's reaction on non-maintainer uploads
STATE: APPROVAL
The policy on doing non-maintainer releases is currently not very detailed.
As doing non-maintainer releases is getting quite common I suggest to
specify more details in
10 matches
Mail list logo
