From: George Shapovalov <george@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] getting sus-2.0.1 marked stable
Date: Fri, 1 Aug 2003 14:22:01 -0700 [thread overview]
Message-ID: <200308011422.02526.george@gentoo.org> (raw)
In-Reply-To: <3F2AB1EF.9000002@gentoo.org>
I prefer getting test reports added to the same bug, - this is why we got
RESOLVED/TEST_REQUEST after all! (the bug is already "invisible" in normal
mode, but easily searchable - by "Assigned To" and its status, quite handy
for sweeping updates).
After I collect sufficient amount of reports (depending on whether it is a
fix, update, are there any otyher problems reported and other stuff..) I mark
the package stable and *close* the bug (its becoming now CLOSED, still
keeping "minor status" of TEST-REQUEST although).
Just my 2 cents on how one can keep track of things without expanding number
of bugs :).
George
On Friday 01 August 2003 11:31, Kumba wrote:
> Usually you file another bug in that case. While not technically a
> "bug" bug, it still lets us keep track of those kind of needed updates.
>
> --Kumba
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-01 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 17:57 [gentoo-dev] getting sus-2.0.1 marked stable William Hubbs
2003-08-01 18:31 ` Kumba
2003-08-01 21:22 ` George Shapovalov [this message]
2003-08-01 19:37 ` Svyatogor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200308011422.02526.george@gentoo.org \
--to=george@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox