begin  quoting Carlos R. Mafra as of Sun, Aug 23, 2009 at 01:08:13AM +0200:
> SJS wrote:
> > Are patches expected to be culled from the list and added automatically,
> > or are they to be posted to the list and tried out by a few folks, and
> > if they work out/don't introduce new bugs, get added to the blessed
> > repository?
> 
> Your questions are pertinent but they can be answered only by
> someone who has the power to make decisions, do you agree?

Not so much.

Given that the web-page has a placeholder, but nothing there, I would
surmise that the "authoratative" answer is "suggest something". Maybe
I'm just ignorant, and can thus be enlightened by almost anyone; maybe
the problem is that everyone is running around with their own version
of what 'ought' to be, all conflicting.

> > How do you all keep track of 90 workspaces? After a dozen or so, I'm
> > just lost.
> 
> If wmaker has an allowed limit of 100 workspaces, it must _not_
> crash in the 82nd. If it crashes somehow, that is a bug and
> must be fixed even though that does not happen often.
> And that was fixed already 4 (!) months ago by Samir.

A fine answer, but to a question somewhat different than I had asked. :)

[snip]
> Window Maker is already very stable and I understand that
> its characteristic time frame is longer because of that.
> But that period of silence should happen _after_ known
> bug fixes are applied, not before.

According to the change log[1], the last bunch of fixes was applied nine
months ago.  Stuff that was fixed only four months ago couldn't have
been applied then, at least, not without closed timelike paths. :)

Obviously, John needs a couple of "integration lieutenants" to apply patches
to the baseline, or at least get them into a "testing" branch.

And what *is* a reasonable 'patch latency', for either an acceptance or a
rejection?  Two weeks? Six months? Thirty-seven hours, fourteen minutes, and
fifty-two point three seconds?

[1] http://hg.windowmaker.info/wmaker/log/1600

-S.


-- 
To unsubscribe, send mail to [email protected].

Reply via email to