[oe] [oe-commits] org.oe.dev - Ignore false toggle signals (work-around for OE#3390).

[Paul Sokolovsky]

Hello,

On Wed, 20 Feb 2008 11:15:45 +0100
Stanislav Brabec <utx at penguin.cz> wrote:

> Paul Sokolovsky wrote:
> 
> > > On Wed, 20 Feb 2008 00:16:17 +0100
> > > "utx commit" <openembedded-commits at lists.openembedded.org> wrote:
> > > 
> > > > - Ignore false toggle signals (work-around for OE#3390).
> > > > - Fixed default ALSA state for SL-Cxx00 (OE#2617).
> > > > - Do not alter incorrect mixer levels by zaurus-mixer-callback.
> > > > - Allow to disable rotation by touch ~/.norot.
> > > > - Fixed detection of panel_user.
> > > > 
> > > > Author: utx at openembedded.org
> > > 
> > > Stanislav, congratulations on getting commit access to OE!
> > > There're few guidelines for developers at
> > > http://www.openembedded.org/wiki/Policies . In particular,
> > > adhering to http://www.openembedded.org/wiki/CommitPolicy allows
> > > for easy peer review and per-package commit search.
> 
> I seen bad formatting in http://monotone.openembedded.org/ and
> gathered bad format of the message. Further messages will be correct
> (I hope).
> 
> My current fixes were done long time ago and ported several times, so
> I no more had one patch per particular change. All future changes will
> follow the rule "each change as separate changeset".
> 
> Note that the policy is missing "Closing bugs policy". Bug was
> reported against Angstrom, now it is fixed in OE.dev. Should the bug
> be closed now, or after backporting the fix to stable Angstrom?

The idea of Angstrom Release bugs (rooted at
http://bugs.openembedded.org/show_bug.cgi?id=1573 ) is to provide list
of known issues to the end user. End user sees only release images and
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.

It practice that means that developers should annotate the bug with
"pushed to .dev", "RFCed for merging to stable", "pushed to stable",
and ultimately, "package in feed, closing".

There're possibly other ways to make process more explicit, for
example, there're FIXED and CLOSED status in bugzilla, so it could be
FIXED when fix committed to main branch, and closed once fix is
confirmed to have solved the issue on user system. But CLOSED is not
used in existing OE bug process, and I'm in no authority to propose it
specifically for Angstrom - even the workflow above is pretty complex,
not really followed much and used to raise misunderstandings with other
bug maintainers.

> 
> -- 
> Stanislav Brabec
> http://www.penguin.cz/~utx/zaurus
> 



-- 
Best regards,
 Paul                          mailto:pmiscml at gmail.com