> For exactly this reason. We want to focus on fixing bugs for 3.3. Having
> to commit to yet another branch at this time would be a distraction,
> as would having to pay attention to feature patches going in to default.
> If the active committers are working on bug fixes, then no features
> woul
On 06/29/2012 02:23 AM, Jesus Cea wrote:
> 3.3 is out. I think this is a waste of time. And even if people is
> working with HG private clones, they can't test using the buildbots
> neither mark a bug as fixed in the tracker.
This is also a nice improvement that Mercurial enables, you can commit
y
On Fri, Jun 29, 2012 at 12:13 PM, R. David Murray wrote:
> There is still nothing stopping people from posting new features to
> the tracker, so there is no reason that non-committer workflow needs
> to change, they just may need to wait a bit longer for feedback...which
> they'd have to do regard
2012/6/28 Jesus Cea :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Python 3.3 is currently in beta, so the rythm of new patches in
> "default" will decrease and people with new features MUST wait until
> 3.3 is out. I think this is a waste of time. And even if people is
> working with HG p
On Fri, 29 Jun 2012 02:23:12 +0200, Jesus Cea wrote:
> Python 3.3 is currently in beta, so the rythm of new patches in
> "default" will decrease and people with new features MUST wait until
> 3.3 is out. I think this is a waste of time. And even if people is
> working with HG private clones, they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Python 3.3 is currently in beta, so the rythm of new patches in
"default" will decrease and people with new features MUST wait until
3.3 is out. I think this is a waste of time. And even if people is
working with HG private clones, they can't test usin
