Re: [lng-odp] TigerMoth_LTS brach
Hi, On 28 April 2018 at 20:32, Bill Fischofer wrote: > > 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? It is handled by a distro itself. We support neither deb nor rpm packages. -- With best wishes Dmitry
Re: [lng-odp] TigerMoth_LTS brach
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 > 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 >
Re: [lng-odp] TigerMoth_LTS brach
Hi, On 28 April 2018 at 16:44, Bill Fischofer 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. -- With best wishes Dmitry
Re: [lng-odp] TigerMoth_LTS brach
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 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 > > >
Re: [lng-odp] TigerMoth_LTS brach
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 >
