[python-committers] Speaking of noticing tracker activity
In the recent thread on python-dev Nick mentioned our dependence on people noticing active contributors on the tracker. In that regard I'd like to recommend people take a look at the work of Martin Panter (vadmium). --David ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Speaking of noticing tracker activity
On 21.07.15 17:06, R. David Murray wrote: In the recent thread on python-dev Nick mentioned our dependence on people noticing active contributors on the tracker. In that regard I'd like to recommend people take a look at the work of Martin Panter (vadmium). Me too. Martin starts contributing patches about a year ago. About half-year ago he increased his activity and patches become less trivial. I have counted about 46 committed patches authored by Martin (16 of them were committed by me). But he also was well known as helpful patch reviewer and participant of discussions on the tracker for a long time before that. I would like to offer granting Martin commit privileges if he is interesting in this. ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Speaking of noticing tracker activity
On Tue, Jul 21, 2015 at 8:28 AM, Serhiy Storchaka wrote: > I would like to offer granting Martin commit privileges if he is > interesting in this. +1 vote from me too. I have noticed number of comments, helpful reviews and patches from Martin Panter. -- Senthil ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] [Python-Dev] Reminder: Python 3.5 beta 4 is tagged in one week
Cool. http://bugs.python.org/issue21750 is in a bad state right now.
I landed a patch to fix it, which when exposed to users had some
defects. I'm working on a better patch now, but need to either roll
the prior patch completely back, or get the new one landed before the
next beta. I hope to have that up for review later today {fingers
crossed} - will that be soon enough, or should I look up how to easily
revert stuff out with hg?
-Rob
On 18 July 2015 at 22:24, Larry Hastings wrote:
>
>
> Approximately a week from when I post this, I'll be tagging Python 3.5 beta
> 4, which is the last beta before we go to release candidates. Please wind
> up all your bug fixes soon, I'd really like checkins to 3.5 to stop soon.
>
> And a minor reminder: when we hit Release Candidate 1, I'll be switching the
> canonical repo for 3.5 to a public Bitbucket repo. Any bug fixes that go in
> between RC 1 and final will only be merged using Bitbucket "pull requests".
>
> The new workflow experiment continues,
>
>
> /arry
>
> ___
> Python-Dev mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/robertc%40robertcollins.net
>
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] [Python-Dev] Reminder: Python 3.5 beta 4 is tagged in one week
On 07/21/2015 06:35 PM, Robert Collins wrote:
Cool. http://bugs.python.org/issue21750 is in a bad state right now.
I landed a patch to fix it, which when exposed to users had some
defects. I'm working on a better patch now, but need to either roll
the prior patch completely back, or get the new one landed before the
next beta. I hope to have that up for review later today {fingers
crossed} - will that be soon enough, or should I look up how to easily
revert stuff out with hg?
If you want to undo it, "hg backout" is the command you want. In
general it's best to not check in broken stuff.
//arry/
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] [Python-Dev] Reminder: Python 3.5 beta 4 is tagged in one week
On 22 July 2015 at 05:08, Larry Hastings wrote:
>
>
> On 07/21/2015 06:35 PM, Robert Collins wrote:
>
> Cool. http://bugs.python.org/issue21750 is in a bad state right now.
>
> I landed a patch to fix it, which when exposed to users had some
> defects. I'm working on a better patch now, but need to either roll
> the prior patch completely back, or get the new one landed before the
> next beta. I hope to have that up for review later today {fingers
> crossed} - will that be soon enough, or should I look up how to easily
> revert stuff out with hg?
>
>
> If you want to undo it, "hg backout" is the command you want. In general
> it's best to not check in broken stuff.
Thanks. And yes, naturally - we didn't realise it was broken. Passing
tests != fit for purpose.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Speaking of noticing tracker activity
On 22 July 2015 at 02:09, Senthil Kumaran wrote: > > On Tue, Jul 21, 2015 at 8:28 AM, Serhiy Storchaka > wrote: >> >> I would like to offer granting Martin commit privileges if he is >> interesting in this. > > +1 vote from me too. I have noticed number of comments, helpful reviews and > patches from Martin Panter. +1 from me as well. I was actually thinking of Martin when I wrote the comment David referenced, but hadn't done the research to look into his wider involvement in tracker discussions. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
