Le 29/04/2025 à 14:33, Pavel Sanda a écrit :
Another thing I would like to propose to stop endlessly postponing major milestones. Our bug lists grew over reasonable size.In particular we could drop the milestone altogether if bug 1) already had 2.4.0 milestone in the past and 2) does not have patch attached and 3) no one will respond to gently ping for finishing in 2.5 (or at least explicitly plans to address it in 2.6) and (4? not sure about this one) there was no reasonable debate/progress in comments during 2.5 dev cycle And similar policy for 2.4.x milestones. If something already had 2.3.x milestone and no progress since then, lets drop the milestone. I spend quite some time sorting out bugs for 2.4.0 and its' waisting time for every new relase if no one touched the bug for a half a decade or more. Moreover it makes it harder to focus on bugs which are more recent/relevant.
As someone who just went through the 2.5 bugs list, I agree to 1-4. JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org https://lists.lyx.org/mailman/listinfo/lyx-devel
