On Sat, Apr 28, 2018 at 9:20 AM, Dmitry Eremin-Solenikov < dmitry.ereminsoleni...@linaro.org> wrote:
> Hi, > > On 28 April 2018 at 16:44, Bill Fischofer <bill.fischo...@linaro.org> > wrote: > > If we're going to be doing formal distributions each of these should have > > their own branch which are created off of the main base release branch. > So > > TigerMoth_LTS is the "master" branch and it can have sub-branches for > > various distributions created from it. This permits distributions to > control > > which service level(s) are included as well as handling > distribution-unique > > service items or other issues. > > This seems too complicated. Why would we have special branches for > individual distributions? We should have separate single tigermoth_lts > branch. It should have commits cherry-picked from master, that are > suiatable for stable releases (suitability depends on exact 'stable' or > 'lts' definition). From my point of view these commits should contain only > bugfixes without any additional changes. > Agreed, LTS == bugfixes only. Functional enhancements go into the next release. Distributions have unique packaging. What if that packaging needs to be changed either because of an error in creating it or else a change in packaging requirements on the part of the distro? > > -- > With best wishes > Dmitry >
