On 04/18/19 09:17, liyi 00215672 wrote: > Hi Guys, > Backgroud: If we choose one stable-tag as our own UEFI codebase, however > after 3 years, there are so many new features(but we don't need) will be > added into EDK2 main tree. > > Requestion: Could EDK2 community plan or maintain "LTS version" concept like > Linux? On LTS version , we only make bug fix or security-related.
This question can be approached in two ways. (1) Introduce stable *branches* to the development model. Those would be forked off at the stable tags (well, at some of them). Stable branches are pretty usual with other open source projects. Unfortunately, they need a bunch of additional work. So when anyone asks, "can you maintain a stable branch for us", the default answer is to ask back, "can you contribute human resources for stable branch maintenance". :) In addition, releases (tags) on stable branches need heavier process and heavier testing. Regressions on stable branches are really bad. The community needs to invent (or, well, "steal") rules for what qualifies for stable branches and what doesn't. (2) I'm a very strong believer in one grand unified git history for *everything* in edk2. (Personally I even think that edk2-platforms should exist within edk2, but I digress.) The reason is very simple: if you want to ignore progress on some modules, you can easily do that [*] even if the git repo is comprehensive. However, if you split things to separate repos, then *reconstructing* a comprehensive history (and navigating / bisect it for bug analysis) is basically *impossible*. Put differently, it is easy to throw away information if you don't need it, but you can't conjure it up from thin air when you do need it. [*] If you decide you don't want module Foo to advance beyond commit Bar for you, then you can simply check out the Foo module into your git working directory (and index) at commit Bar, just before you launch your build: git checkout Bar -- Path/To/Module/Foo You can repeat this command arbitrarily many times, with different commits for different modules, before you launch the build. Thanks Laszlo -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#39321): https://edk2.groups.io/g/devel/message/39321 Mute This Topic: https://groups.io/mt/31222094/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
