On Fri, Feb 21, 2020 at 7:28 PM John M. Harris Jr
<johnmh(a)splentity.com>
wrote:
>
>
> On Friday, February 21, 2020 2:31:14 AM MST jkonecny(a)redhat.com wrote:
>
> > Hi,
> >
> >
> >
> > Thanks a lot for this change. 00:00 is always confusing to deal with.
> >
> >
> >
> > Jirka
> >
> >
> >
> > On Thu, 2020-02-20 at 14:04 -0500, Mohan Boddu wrote:
> >
> >
> >
> > > Hi all,
> > >
> > >
> > >
> > > It has been brought to our attention that release freezes starting at
> > > 00:00 UTC has been confusing for a lot of people. So, we decided to
> > > change it to 14:00 UTC.
> > >
> > >
> > >
> > > The freeze dates are not going to change, just the time when freeze
> > > starts is going to change. Fedora 32 schedule [1] has been updated to
> > > reflect the changed time.
> > >
> > >
> > >
> > > [1]
https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html
> > >
> > >
> > >
> > > Thanks,
> > > Mohan Boddu.
>
>
>
> I really must disagree. 0000 UTC is at least aligned with something. I
> cannot imagine what 1400 UTC was chosen to align with, or how this will
> be any less confusing. This seems like it'd only be *more* confusing.
>
>
14:00 UTC is 9:00 EST, so it basically means to everyone: do
everything the day before. And 00:00 is confusing because people
interpret it either the day before or the day after. It's a "special"
time that nobody should ever schedule anything people need to care
about at.
That's simply not true. 0000 UTC is midnight UTC. That is not difficult to
grasp. I certainly understand the mappings, which is why this is even more
confusing. Why was 1400 chosen?
--
John M. Harris, Jr.
Splentity