On 6/3/24 03:04, José Matos wrote:
On Sun, 2024-06-02 at 22:53 -0400, Richard Kimberly Heck wrote:
I've merged 2.4.x into 2.4.1-devel. I should have been doing this
periodically but didn't. There were quite a few conflicts,
unsurprisingly. I believe I have resolved them all properly, and I've
spot-checked several commits. But you might want to have a look and
make sure I didn't mess anything up.
Going forward, this should not be as much of an issue, since commits
to 2.4.x will be few. And hopefully, we won't need an emergency
release, and I can merge 2.4.1-devel into 2.4.x before long.
Riki
An interesting idea that comes from KDE is that bugfix releases use a
Fibonacci series (assuming F_0=1).
The first bug fix release (.1) is done one week after the stable
release (.0).
The second release is done 2 weeks after .1.
The third release is done 3 weeks after .2.
The fourth release is done 5 weeks after .3.
...
My point here is to establish some kind of deadline.
Something like "unless some emergency bug comes 2.4.1 is (more or less)
scheduled for the end of the month".
There are quite a few updates already, so a release at the end of the
month would make sense. So would some kind of regular schedule.
Riki
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
