Excerpts from Jeremy Stanley's message of 2018-07-05 17:34:59 +:
> On 2018-07-05 13:23:57 -0400 (-0400), Doug Hellmann wrote:
> [...]
> > I wonder if it would be useful to move that step of determining the
> > topic out to a hook, so that project-specific logic could be applied
> > as part of
Paul Belanger writes:
> Greetings,
>
> Over the last few weeks I've been helping the RDO project migrate away from
> zuulv2 (jenkins) to zuulv3. Today all jobs have been migrated with the help of
> the zuul-migrate script. We'll start deleting jenkins bits in the next few
> days.
>
> I wanted
On 07/05/2018 09:13 AM, Jeremy Stanley wrote:
> On 2018-07-05 09:03:44 -0700 (-0700), Andrew Grimberg wrote:
>> On 07/04/2018 06:57 PM, Jeremy Stanley wrote:
> [...]
>>> For that matter, setting the topic based on the local branch
>>> name could also get tossed while we're at it, and just keep the
On 2018-07-05 13:23:57 -0400 (-0400), Doug Hellmann wrote:
[...]
> I wonder if it would be useful to move that step of determining the
> topic out to a hook, so that project-specific logic could be applied
> as part of submitting a patch?
In the way of spitballing some alternatives, we could have
Excerpts from Jeremy Stanley's message of 2018-07-05 16:13:16 +:
> On 2018-07-05 09:03:44 -0700 (-0700), Andrew Grimberg wrote:
> > On 07/04/2018 06:57 PM, Jeremy Stanley wrote:
> [...]
> > > For that matter, setting the topic based on the local branch
> > > name could also get tossed while
Greetings,
Over the last few weeks I've been helping the RDO project migrate away from
zuulv2 (jenkins) to zuulv3. Today all jobs have been migrated with the help of
the zuul-migrate script. We'll start deleting jenkins bits in the next few days.
I wanted to get down some things I've noticed in
On 2018-07-05 09:03:44 -0700 (-0700), Andrew Grimberg wrote:
> On 07/04/2018 06:57 PM, Jeremy Stanley wrote:
[...]
> > For that matter, setting the topic based on the local branch
> > name could also get tossed while we're at it, and just keep the
> > -t option for directly specifying a change
On 07/04/2018 06:57 PM, Jeremy Stanley wrote:
>> And potentially controversially; support other workflows and
>> options outside of the OpenStack workflow. Although maybe not
>> directly, and still keeping the OpenStack one as the default.
>
> I'd love to know what about git-review is focused on
Jeremy already articulated my thoughts well; I don't have much to add.
But I think it's important to reiterate that I find it extremely
valuable that git-review perform its function ("push changes to Gerrit")
simply and reliably.
There are certainly projects we've created which are neglected due
On July 3, 2018 7:39 am, Tristan Cacqueray wrote:
[...]
There is a lot to do and it will be challening. To that effect, I would
like to propose an initial meeting with all interested parties.
Please register your irc name and timezone in this etherpad:
10 matches
Mail list logo
