Policy for commits to master

[Scott Kostyshak]

On Mon, Oct 31, 2022 at 07:33:52PM +0100, Jürgen Spitzmüller wrote:
> Am Montag, dem 31.10.2022 um 13:48 -0400 schrieb Scott Kostyshak:
> > One immediate issue is whether we can commit features. I think there
> > is
> > support for "opening" master up and allowing features to be
> > committed. I
> > think this makes sense because so much time has gone by, and also I
> > will
> > not have much time until January anyway so the final stages of the
> > release are not near. However, I think it's important we're a bit
> > more
> > conservative than usual. I think everyone agrees that master is not a
> > sandbox, but I think we should be even more careful. I propose the
> > following general guidelines:
> 
> Thanks, Scott. I have tested my feature carefully, and committed now. I
> am ready to follow the guidelines.

Great, thanks for your work on that feature! It will be nice to have it in 2.4.0.

Scott
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.lyx.org/pipermail/lyx-devel/attachments/20221031/55cf0fe7/attachment.asc>