Re: widgets plan proposal

> > I would rather have the same strict policy you have set out for the
engine.  
> > Once the widget tree is declared happy, any changes to that widget tree 
> > should be cleared by consensus before commit.
> 
> Interesting.  How about if I fork of stable branches periodically, and
> you can only commit to those branches with consensus approval?

Yes, how's about simply differentiating between branches rather than
'consensus approval' of patches.

Have 3 branches, like the core.  Testing that's almost an open box for the
devs, unstable that's for applying bug fixes to in the event that they get
rolled back into stable.

Committing to unstable and rolling unstable back into stable should be
'commit by consensus'.  But dev code should not.  It'd be a nightmare
developing like that.
_______________________________________________
http://lists.xwt.org/listinfo/dev