File format increases on master make it hard to test

[Scott Kostyshak]

I've been enjoying testing master, but on the first file format increment, I'll stop a lot of my testing since they're documents I will want to work on with other people.

I have a few documents that only I use and for that I'll try to continue to test master.

I imagine others face the same situation? Is there anything that can be done? I remember that Guillaume used to maintain a lyx-unstable (I think this was the name) where I think he removed the file format updates. How hard would that be to maintain?

I guess ideally anything that doesn't involve a file format bump would also eventually be pushed to 2.4.x, so our testing of 2.4.x should help indirectly to test master, but there are a lot of commits that don't go to 2.4.x (for good reason). I guess an alternative would be to have a master-no-file-format branch, that gets all the commits master does except file format increments? But in this case it seems it would be less work to maintain the lyx-unstable referenced above, so that we don't have to double-commit each time?

Not sure if anything can feasibly be done here, but wanted to ask.

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/20240406/b5b0ff23/attachment.asc>