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.
On Sat, Apr 28, 2018 at 8:04 AM, Maxim Uvarov <maxim.uva...@linaro.org> wrote: > On 28 April 2018 at 14:25, Dmitry Eremin-Solenikov < > dmitry.ereminsoleni...@linaro.org> wrote: > > > Hello, Maxim, > > > > Could you please start pushing pending fixes to tigermoth_lts branch, so > > that > > they can be picked into packaging? > > > > > As we discussed before I plan to release new development tag first and then > cherry-pick commits. In that case we can have good testing for commits > which we are cherry-picking. > For now almost all commits for master can go to tigermoth_lts. Do you pick > for packaging branch or some specific tag? > > Maxim. > > > > -- > > With best wishes > > Dmitry > > >
