On Fri, Aug 2, 2013 at 8:13 PM, Nick Coghlan wrote:
>
>
> On 3 Aug 2013 10:25, "Larry Hastings" wrote:
> >
> > On 08/02/2013 02:00 PM, Antoine Pitrou wrote:
> >>
> >> "Forward" means what? Earlier or later?
> >> (intuitively, I'd say "earlier", but that doesn't seem very consistent
> >> with your
On 3 Aug 2013 10:25, "Larry Hastings" wrote:
>
> On 08/02/2013 02:00 PM, Antoine Pitrou wrote:
>>
>> "Forward" means what? Earlier or later?
>> (intuitively, I'd say "earlier", but that doesn't seem very consistent
>> with your explanations)
>
>
> Your intuition is the opposite of mine. When I mo
On 08/02/2013 02:00 PM, Antoine Pitrou wrote:
"Forward" means what? Earlier or later?
(intuitively, I'd say "earlier", but that doesn't seem very consistent
with your explanations)
Your intuition is the opposite of mine. When I move dates "forward", I
increase the date / number / etc. So I w
On Aug 02, 2013, at 11:00 PM, Antoine Pitrou wrote:
>No need to IMO, but you mention it when sending your reminder message.
>(most core developers certainly spare themselves the hassle of reading
>PEP 101 - or, once they've read it, they forget it as quickly as
>possible :-))
FWIW, I've always co
On Jul 29, 2013, at 11:25 PM, Brad Knowles wrote:
>The postmaster/listmaster folks could potentially act as "emergency backup"
>moderators, much like we do for the mailman-* lists, if there was a need for
>additional people to help out. However, I suspect this additional work would
>need to remai
Le vendredi 02 août 2013 à 13:25 -0700, Larry Hastings a écrit :
> From PEP 101, "Doing Python Releases 101":
> > IT IS HIGHLY RECOMMENDED THAT YOU AT LEAST TAG THE TREE 24 HOURS
> > BEFORE A FINAL RELEASE. This will give the Experts enough time to
> > do their bits before the announcement goes o
In article <51fc15c2.9040...@hastings.org>,
Larry Hastings wrote:
> From PEP 101, "Doing Python Releases 101":
> > IT IS HIGHLY RECOMMENDED THAT YOU AT LEAST TAG THE TREE 24 HOURS
> > BEFORE A FINAL RELEASE. This will give the Experts enough time to
> > do their bits before the announcement goe
On 08/02/2013 01:25 PM, Larry Hastings wrote:
But speaking of adjusting the schedule, I'm also considering changing bumping
all the remaining release dates forward by
a day. Currently all the releases are on Saturdays, which means we always tag
on Friday. Ned Deily suggests instead we
tag on
On Fri, Aug 2, 2013 at 4:25 PM, Larry Hastings wrote:
> From PEP 101, "Doing Python Releases 101":
>
> IT IS HIGHLY RECOMMENDED THAT YOU AT LEAST TAG THE TREE 24 HOURS
> BEFORE A FINAL RELEASE. This will give the Experts enough time to
> do their bits before the announcement goes out.
>
> The sch
On 08/02/2013 01:00 PM, Ned Deily wrote:
Hmm. I understand this is an alpha but I was hoping to get a few more
fixes in today. Perhaps, in the future, we can be more clear about
exactly when the code freeze time (tag time) is vs a release time.
From a developer point of view, the former is im
In article <51fc0bd9.1000...@hastings.org>,
Larry Hastings wrote:
> By the way, it looks like 3.4a1 will be basically on time. I've triaged
> all the extant release blockers, so I don't have any right now. (Mostly
> just marking them as "deferred blocker"...) I plan to tag today for a
> rel
On 08/01/2013 04:14 PM, Victor Stinner wrote:
Is it ok to do such changes between the alpha4 and beta1?
Yes. We don't hit feature-freeze until beta 1.
But it's best to get your changes in earlier, so they can be in one (or
more) alphas. And in case you discover something wrong with your
a
12 matches
Mail list logo
