You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What's the criteria to mark a patch eligible to be backported? "Security fixes only" or "critical fixes only" or "no API/ABI change"? I don't know if the administration has made a policy about such eligibility for backporting, but if not we are really not in a position to make such decisions ourselves.
What's the criteria to mark a patch eligible to be backported? "Security fixes only" or "critical fixes only" or "no API/ABI change"? I don't know if the administration has made a policy about such eligibility for backporting, but if not we are really not in a position to make such decisions ourselves.
I'm not aware of any public information regarding this, other than "the baseline is a real thing, and has been decided", so there's still a ton of details to work out. I'm filing the issue mainly as a note to myself and other concerned devs, so we don't forget.
工信部会同一些厂商,针对部分软件包制定了版本基线要求,未来的新世界商业发行版都需要遵循。
由于社区发行版的包版本并不会被此基线卡死,未来与这些系统的互操作性势必逐渐下降。鉴于可以预见一部分闭源软件会瞄准此基线,并且用户十分可能依赖这些软件,可以想见大部分活跃的 LoongArch 社区发行版都将有需求(额外)支持此基线;为与正常追踪主线的版本在功能上对齐,维护针对工信部基线的 backport 补丁集在可预见的未来不可避免。
The text was updated successfully, but these errors were encountered: