On 30/04/18 21:00, Salz, Rich wrote:
> >>I would normally start around 12.00 UTC, but could push it a bit
> later
> > if it works better for you.
> >
> > So that's 7am, it would be best to delay an hour.
> >
>
> Ok, lets make it 13.00 UTC.
>
> Gaah, forg
>>I would normally start around 12.00 UTC, but could push it a bit later
> if it works better for you.
>
> So that's 7am, it would be best to delay an hour.
>
Ok, lets make it 13.00 UTC.
Gaah, forgot about daylight savings. 12.00 UTC is 8am my time. Keep
On 30/04/18 20:07, Salz, Rich wrote:
>>Nobody else has stepped forward. Are you still available for this?
>
> Sure.
>
>>I would normally start around 12.00 UTC, but could push it a bit later
> if it works better for you.
>
> So that's 7am, it would be best to delay an hour.
>
>Nobody else has stepped forward. Are you still available for this?
Sure.
>I would normally start around 12.00 UTC, but could push it a bit later
if it works better for you.
So that's 7am, it would be best to delay an hour.
___
opens
On 27/04/18 12:12, Salz, Rich wrote:
>>As normal we are planning a new beta release on Tuesday. This means that
>>we will be freezing the repo from Monday afternoon (UTC).
>
> I'm in US but available if nobody "closer" can do it.
Nobody else has stepped forward. Are you still availabl
>As normal we are planning a new beta release on Tuesday. This means that
>we will be freezing the repo from Monday afternoon (UTC).
I'm in US but available if nobody "closer" can do it.
___
openssl-project mailing list
openssl-project@openss
As normal we are planning a new beta release on Tuesday. This means that
we will be freezing the repo from Monday afternoon (UTC).
Richard will not be available to review the release so I'm looking for a
volunteer to fill that role. Any takers?
Thanks
Matt
___
