Zitat von Petri Lehtinen :
Georg Brandl wrote:
From the release of rc1, I will keep the code that will become 3.3 in
a separate repo, so that commits to "default" on cpython *won't* go
into 3.3. You will have to notify me of all commits that you think
*should* go there, so that I can cherry-p
Georg Brandl wrote:
> From the release of rc1, I will keep the code that will become 3.3 in
> a separate repo, so that commits to "default" on cpython *won't* go
> into 3.3. You will have to notify me of all commits that you think
> *should* go there, so that I can cherry-pick them. Not all bugfi
Well, I can certainly push the branch back to the main repo, but I really
don't want anyone else committing to it.
Georg
On 21.08.2012 00:05, Victor Stinner wrote:
Why not creating a 3.3.0 branch to prepare the release instead of a different
repository?
Victor
Le 19 août 2012 13:05, "Georg Br
Why not creating a 3.3.0 branch to prepare the release instead of a
different repository?
Victor
Le 19 août 2012 13:05, "Georg Brandl" a écrit :
> Dear committers,
>
> if the buffer/array-related blockers are resolved in time, the rc1
> will be released one week from now.
>
> Since some people a
Dear committers,
if the buffer/array-related blockers are resolved in time, the rc1
will be released one week from now.
Since some people asked: at the moment we are not in the RC phase yet,
so fixing bugs is allowed, but it would be advisable to have a second
committer review any nontrivial fix
