On Mon, 2015-08-17 at 13:36 +, Jeremy Stanley wrote:
> On 2015-08-17 15:25:07 +0200 (+0200), Thierry Carrez wrote:
> [...]
> > I see Doug, Robert, Clark and myself as necessary to the
> > discussion
> [...]
>
> It would also be great to get some of the operators and/or package
> maintainers in
Excerpts from Alan Pevec's message of 2015-08-18 01:36:05 +0200:
> > The only alternative seems to be to have on-demand stable-branch
> > tagging. The main drawbacks of that option are that consumers of the
> > stable branch are unnecessarily limited to specific tagged commits, and
> > depend on va
On 2015-08-18 01:36:05 +0200 (+0200), Alan Pevec wrote:
[...]
> OSSA merge could trigger an async release proposal too.
True, now that we're putting the advisories through Gerrit, that's
certainly an available option.
--
Jeremy Stanley
> The only alternative seems to be to have on-demand stable-branch
> tagging. The main drawbacks of that option are that consumers of the
> stable branch are unnecessarily limited to specific tagged commits, and
> depend on various project teams to remember to push them.
As Doug suggested, stable
Thierry Carrez wrote:
> We need to make progress on this so that the tooling is ready when we
> switch to stable branches at the end of Liberty. Should we discuss it
> live at a cross-project meeting ? I see Doug, Robert, Clark and myself
> as necessary to the discussion, but anyone else is welcome
On 2015-08-17 15:25:07 +0200 (+0200), Thierry Carrez wrote:
[...]
> I see Doug, Robert, Clark and myself as necessary to the
> discussion
[...]
It would also be great to get some of the operators and/or package
maintainers involved since they were the ones arguing against the
original and much sim
Hi!
This discussion died without a clear way forward...
The "automatically tagging every commit" option, described by Robert as
"the only sensible route", results according to Clark in so many tags
you end up polluting the ref space and making it unusable by humans.
However, we are lacking other
Excerpts from Alan Pevec's message of 2015-08-05 16:14:32 +0200:
> >> > > > To give you an idea, if we enabled that for Kilo we'd be at Nova
> >> > > > 11.0.80
> >> > > > (kilo) and Nova 10.0.218 (juno).
> >> > > I am not a fan of doing this second option at all. We would be
> >> > > polluting
>
>> > > > To give you an idea, if we enabled that for Kilo we'd be at Nova
>> > > > 11.0.80
>> > > > (kilo) and Nova 10.0.218 (juno).
>> > > I am not a fan of doing this second option at all. We would be polluting
>> > > the ref space of our repos with redundant information making the output
>> > >
Excerpts from Clark Boylan's message of 2015-08-04 09:28:00 -0700:
>
> On Tue, Aug 4, 2015, at 06:22 AM, Doug Hellmann wrote:
> > Excerpts from Clark Boylan's message of 2015-08-03 11:54:06 -0700:
> > > On Mon, Aug 3, 2015, at 05:46 AM, Thierry Carrez wrote:
> > > > Hi everyone,
> > > >
> > > > A
On Tue, Aug 4, 2015, at 06:22 AM, Doug Hellmann wrote:
> Excerpts from Clark Boylan's message of 2015-08-03 11:54:06 -0700:
> > On Mon, Aug 3, 2015, at 05:46 AM, Thierry Carrez wrote:
> > > Hi everyone,
> > >
> > > A month ago the stable branch team decided to move away from
> > > synchronized s
Excerpts from Clark Boylan's message of 2015-08-03 11:54:06 -0700:
> On Mon, Aug 3, 2015, at 05:46 AM, Thierry Carrez wrote:
> > Hi everyone,
> >
> > A month ago the stable branch team decided to move away from
> > synchronized stable point releases and enable continuous stable branch
> > delivery
Clark Boylan wrote:
> On Mon, Aug 3, 2015, at 05:46 AM, Thierry Carrez wrote:
>> In order to make this work, it looks like we'd require:
>>
>> * pbr changes so that it supports a mode where every commit on the
>> branch increments .Z
>>
>> * infra changes to automatically push the corresponding tag
On Mon, Aug 3, 2015, at 05:46 AM, Thierry Carrez wrote:
> Hi everyone,
>
> A month ago the stable branch team decided to move away from
> synchronized stable point releases and enable continuous stable branch
> delivery instead.
>
> The end goal is that every commit on a stable branch for a "serv
On 4 August 2015 at 06:06, Doug Hellmann wrote:
> Excerpts from Thierry Carrez's message of 2015-08-03 18:11:53 +0200:
>> Jeremy Stanley wrote:
>> > On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote:
>> > [...]
>> >> In order to make this work, it looks like we'd require:
>> >>
>> >> * pb
On 2015-08-03 16:42:06 + (+), Ian Cordasco wrote:
> Auto-tagging seems to be the least amount of work. That could be
> done as a post-commit hook or post-receive (depending on where we
> implement it) upstream.
Well, not as a git hook but we would likely run it as a CI job in
zuul's post p
Excerpts from Thierry Carrez's message of 2015-08-03 18:11:53 +0200:
> Jeremy Stanley wrote:
> > On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote:
> > [...]
> >> In order to make this work, it looks like we'd require:
> >>
> >> * pbr changes so that it supports a mode where every commit o
On 8/3/15, 11:11, "Thierry Carrez" wrote:
>Jeremy Stanley wrote:
>> On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote:
>> [...]
>>> In order to make this work, it looks like we'd require:
>>>
>>> * pbr changes so that it supports a mode where every commit on the
>>> branch increments .
Jeremy Stanley wrote:
> On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote:
> [...]
>> In order to make this work, it looks like we'd require:
>>
>> * pbr changes so that it supports a mode where every commit on the
>> branch increments .Z
>>
>> * infra changes to automatically push the cor
On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote:
[...]
> In order to make this work, it looks like we'd require:
>
> * pbr changes so that it supports a mode where every commit on the
> branch increments .Z
>
> * infra changes to automatically push the corresponding tag when the
> comm
Hi everyone,
A month ago the stable branch team decided to move away from
synchronized stable point releases and enable continuous stable branch
delivery instead.
The end goal is that every commit on a stable branch for a "service"
project will get a .Z version increment, and a tag be pushed to m
21 matches
Mail list logo