Re: RFC: reverse the name change for org.oe.stable

[Rolf Leggewie <no2spam@nospam.arcornews.de>]

Richard Purdie wrote:
> We do need a stable branch.

I guess so.  And I don't question that.  I just raise the flag that if
nobody is indeed interested in actually fixing bugs, we should
reconsider having it.  Right now, we have a snapshot with virtually no
activity, not a stable, actively maintained branch.  IMNSHO, OE should
be honest or it will loose credibility.  If we can't support a stable
branch (because supposedly people are too busy), we should not be
suggesting we do.  The openembedded-stable ml and the bug tracker,
together with the many people here who say "We should have a stable
branch, *but* right now I can't work on it" tell a clear story.

> The stable branch people have commented on the use of the bugzilla and I
> can't really see a problem there. 

They say they want mail, fine.

The problem is that they both block mail from bugzilla to the oe-stbale
list (and I am not going to play human gateway) and ignoring it in the
case of koen (who I added specifically as cc for bp flags raised).  I
don't think I should even be doing this.  If people are supporting
stable as the claim stands, there should be at least some activity in
the bug tracker wrt fixing bugs.

* several weeks if not months of no bug triaging from .stable
  causes concern
* no activity after some bug triaging is done for them
  causes real concern
* still no activity after blocking their meta bugs about a month ago
  causes serious concern
* still no activity after sending several reminder mails to the ml
  causes grave concern
* a "do as you please"-attitude after issuing a last warning and still
  no activity after providing them the patches the stable guys should
  have derived themselves if claims of support are to be taken serious

  this falls back on OE

BTW, still no bug triaging and not even the simple activity of looking
through the bugs that have been meticulously prepared.

> technical rather than emotive and discuss the problems before proposing
> inflammatory solutions.

I am absolutely technical.  The choice is simple

a) support it, including at least some work in the bug tracker
b) rename it
c) risk loss of reputation for OE as not living up to claims made

It is one of the three and really that easy.  Unfortunately, it looks
like everybody choosing c) because "we want stable".