вс, 27 июн. 2021 г. в 12:55, Nicholas Clark <nick@ccl4.org>: > We discussed how the .N (>0) releases work. We need to be careful with maint > releases - they are *somewhat like* dev releases, but far more dangerous. > > The current process predates our migration to GitHub, and started with a web > frontend that wrote out an XML file to track "backport votes", and share the > work of deciding what was necessary and safe to backport. We wondered > whether we can make anything simpler by finding features of GitHub that > could help, but we failed to assign an "action item" to any one individual, > so, whoops, it has stalled. I find the scale of this issue underappreciated. In past years, I've asked for a number of fixes to be added to maint releases - and it only worked since I've been around p5p for some time. Chances that any particular eligible fix lands in maint are very slim, either it's author should know the process or someone should notice it and push the issue. Even than, it's far from guaranteed - I remember a commit fixing Coro compilation breakage missing two 5.22 point releases until it finally landed there, despite extensive discussion on this list. It'd be great if PSC could provide a more robust and less error prone process for this. Best regards, Sergey AleynikovThread Previous | Thread Next