Am Di., 25. Feb. 2020 um 20:37 Uhr schrieb Matthew Miller
:
> > Whereas with 12h clocks, I think midnight is 12:00 PM, and noon is 12:00
> > AM? Which is still confusing me after having known about it for decades.
>
> It's the opposite, which furthers your point. :)
That does not seem to be very
On Sat, Feb 22, 2020 at 11:06:30AM +0100, Fabio Valentini wrote:
> I assume 00:00 UTC was confusing for people used to the AM/PM (12h) time
> format instead of the 24h format.
>
> For people used to 24h clocks, it's completely obvious that 00:00 is the
> beginning of the day, and 24:00 is the end
We didn't pick the time at random, 14:00 UTC is the time when Fedora
release gets out. We thought if we are changing the time, we should
align it with the only other time constrained task, that is, Fedora
release.
00:00 UTC is definitely confusing for some people as they complained
about it, but
On Sat, Feb 22, 2020 at 7:58 AM Kevin Kofler wrote:
>
> Neal Gompa wrote:
> > 14:00 UTC is 9:00 EST, so it basically means to everyone: do
> > everything the day before.
>
> "Do everything the day before" is exactly what was confusing about the 00:00
> UTC deadline, so I do not see how the change
Neal Gompa wrote:
> 14:00 UTC is 9:00 EST, so it basically means to everyone: do
> everything the day before.
"Do everything the day before" is exactly what was confusing about the 00:00
UTC deadline, so I do not see how the change to 14:00 UTC fixes the issue.
It is customary to give inclusive
On Sat, Feb 22, 2020, 10:47 Ralf Corsepius wrote:
> On 2/20/20 8:04 PM, 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.
>
> This longs
On 2/20/20 8:04 PM, 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.
This longs for an explanation.
I fail to understand why 14:00 UTC should be less
> On Friday, February 21, 2020 10:52:27 PM MST Miro Hrončok wrote:
> > On 22. 02. 20 1:28, John M. Harris Jr wrote:
> >
> > > I really must disagree.
> >
> >
> > In my opinion, once you simply disagree with literally everything, your
> > feedback no longer gives any significant meaning for the
On Friday, February 21, 2020 10:52:27 PM MST Miro Hrončok wrote:
> On 22. 02. 20 1:28, John M. Harris Jr wrote:
>
> > I really must disagree.
>
>
> In my opinion, once you simply disagree with literally everything, your
> feedback no longer gives any significant meaning for the people who
>
On 22. 02. 20 1:28, John M. Harris Jr wrote:
I really must disagree.
In my opinion, once you simply disagree with literally everything, your feedback
no longer gives any significant meaning for the people who receive it. I know
that it is very frustrating when everybody around you seem not
On 2/21/20 9:32 PM, John M. Harris Jr wrote:
That's simply not true. 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?
Midnight of which day? Maybe it doesn't confuse you, but it
On Friday, February 21, 2020 9:03:26 PM MST Neal Gompa wrote:
> On Fri, Feb 21, 2020 at 7:28 PM John M. Harris Jr
> wrote:
> >
> >
> > On Friday, February 21, 2020 2:31:14 AM MST jkone...@redhat.com wrote:
> >
> > > Hi,
> > >
> > >
> > >
> > > Thanks a lot for this change. 00:00 is always
On Fri, Feb 21, 2020 at 7:28 PM John M. Harris Jr wrote:
>
> On Friday, February 21, 2020 2:31:14 AM MST jkone...@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:
> >
On Friday, February 21, 2020 2:31:14 AM MST jkone...@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
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
>
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
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
17 matches
Mail list logo
