On 7/28/2020 7:41 AM, Eric Covener wrote:
> On Tue, Jul 28, 2020 at 4:30 AM Christophe JAILLET
> wrote:
>> Le 27/07/2020 à 14:11, Daniel Ruggeri a écrit :
>>>
>>> On July 27, 2020 2:12:45 AM CDT, Stefan Eissing
>>> wrote:
> Am 25.07.2020 um 00:14 schrieb Daniel Ruggeri :
>
>
On Tue, Jul 28, 2020 at 4:30 AM Christophe JAILLET
wrote:
>
> Le 27/07/2020 à 14:11, Daniel Ruggeri a écrit :
> >
> >
> > On July 27, 2020 2:12:45 AM CDT, Stefan Eissing
> > wrote:
> >>
> >>
> >>> Am 25.07.2020 um 00:14 schrieb Daniel Ruggeri :
> >>>
> >>> Hi, all;
> >>>FYI, I came across
Le 27/07/2020 à 14:11, Daniel Ruggeri a écrit :
On July 27, 2020 2:12:45 AM CDT, Stefan Eissing
wrote:
Am 25.07.2020 um 00:14 schrieb Daniel Ruggeri :
Hi, all;
FYI, I came across an unexpected set of diffs when rebuilding docs
before tagging this morning. Haven't forgotten about T,
On July 27, 2020 2:12:45 AM CDT, Stefan Eissing
wrote:
>
>
>> Am 25.07.2020 um 00:14 schrieb Daniel Ruggeri :
>>
>> Hi, all;
>> FYI, I came across an unexpected set of diffs when rebuilding docs
>before tagging this morning. Haven't forgotten about T, but would
>like to figure out the
> Am 25.07.2020 um 00:14 schrieb Daniel Ruggeri :
>
> Hi, all;
> FYI, I came across an unexpected set of diffs when rebuilding docs before
> tagging this morning. Haven't forgotten about T, but would like to figure
> out the origin of the docs changes (likely my environment). I've started
Hi, all;
FYI, I came across an unexpected set of diffs when rebuilding docs before
tagging this morning. Haven't forgotten about T, but would like to figure out
the origin of the docs changes (likely my environment). I've started a
conversation on docs@ about what I'm seeing.
On 2020/07/22
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel,
On 7/24/20 17:36, Daniel Ruggeri wrote:
> Hey there, Chris;
>
> Fair question - and I don't think I have a handy link describing
> the flow of patch -> trunk -> STATUS backport proposal -> branch
> commit -> release
>
> Generally speaking,
Hey there, Chris;
Fair question - and I don't think I have a handy link describing the
flow of patch -> trunk -> STATUS backport proposal -> branch commit ->
release
Generally speaking, the code goes into trunk and is proposed for
backport into a stable branch via the STATUS file (at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel,
On 7/22/20 19:32, Daniel Ruggeri wrote:
> Hi, all; It's been a while since we've rolled a release and gotten
> fixes/etc in our community's hands. Apologies for not suggesting
> this sooner. How about a T Friday? That will let vote run
On Thu, Jul 23, 2020 at 1:32 AM Daniel Ruggeri wrote:
>
> It's been a while since we've rolled a release and gotten fixes/etc in our
> community's hands. Apologies for not suggesting this sooner. How about a T
> Friday? That will let vote run through the weekend.
+1
Regards;
Yann.
Sure. Go ahead. +1
> On Jul 22, 2020, at 7:32 PM, Daniel Ruggeri wrote:
>
> Hi, all;
> It's been a while since we've rolled a release and gotten fixes/etc in our
> community's hands. Apologies for not suggesting this sooner. How about a T
> Friday? That will let vote run through the weekend.
On 23 Jul 2020, at 01:32, Daniel Ruggeri wrote:
> It's been a while since we've rolled a release and gotten fixes/etc in our
> community's hands. Apologies for not suggesting this sooner. How about a T
> Friday? That will let vote run through the weekend.
+1.
Regards,
Graham
—
Hi, all;
It's been a while since we've rolled a release and gotten fixes/etc in our
community's hands. Apologies for not suggesting this sooner. How about a T
Friday? That will let vote run through the weekend.
--
Daniel Ruggeri
13 matches
Mail list logo
