From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: what is a fixed bug? (was: [oe-commits] org.oe.dev - Ignore false toggle signals (work-around for OE#3390).)
Date: Wed, 20 Feb 2008 19:38:40 +0100 [thread overview]
Message-ID: <fphs3l$jcj$1@ger.gmane.org> (raw)
In-Reply-To: <20080220155339.67aed5d4@widy.localdomain>
Paul Sokolovsky wrote:
> feeds. So, if bug is fixed in source, but corresponding package hasn't
> made to feeds, then per above idea (hopefully pretty obvious and
> no-nonsense), the bug should not be closed.
I disagree (see mail about Angstrom usurping bugs.oe.org).
I have yet to come up with a complete plan how things should work (one
idea fell apart because a partner had to retract their offer). But
let's discuss this piece since it came up: when to consider a normal bug
closed.
The above are really two or more issues.
a) fix the problem itself
b) propagate the fix to A*
c) propagate the fix to PS Distro
IMO, any bug fixed in .dev ought to be closed. If it needs to be
backported or released to A*, then a separate ticket should be opened
(one issue, one bug, remember!). The cloning function from bugzilla can
easily be used for that.
We just face the problem that - unlike launchpad - bugzilla is incapable
of tracking the status according to project for the same issue (open for
ubuntu, closed in debian for example)
next prev parent reply other threads:[~2008-02-20 18:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1JRbhB-0000nu-DN@linuxtogo.org>
2008-02-19 23:58 ` [oe-commits] org.oe.dev - Ignore false toggle signals (work-around for OE#3390) Paul Sokolovsky
2008-02-20 0:04 ` Paul Sokolovsky
2008-02-20 10:15 ` Stanislav Brabec
2008-02-20 13:53 ` Paul Sokolovsky
2008-02-20 18:38 ` Rolf Leggewie [this message]
2008-02-20 19:26 ` what is a fixed bug? (was: [oe-commits] org.oe.dev - Ignore false toggle signals (work-around for OE#3390).) Paul Sokolovsky
2008-02-21 10:57 ` what is a fixed bug? Rolf Leggewie
2008-02-21 12:04 ` Paul Sokolovsky
2008-02-21 12:40 ` Rolf Leggewie
2008-02-21 13:11 ` Paul Sokolovsky
2008-02-21 14:23 ` Rolf Leggewie
2008-02-21 2:34 ` [oe-commits] org.oe.dev - Ignore false toggle signals (work-around for OE#3390) Junqian Gordon Xu
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='fphs3l$jcj$1@ger.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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