[Python-mode] simplified procedure
Hi Barry, thanks for the merges. With respect to the still considerable amount of reports and a possible speed up of it's treatment, please permit some reflexions, how ease the process: - as for pure typos, whitespace, indent-matters IMHO developers should be permitted to push into the trunk without prior notice. - if funktion is changed, newly introduced, we could agree a simplified procedure, saying a delay of three days, so people may object. - in cases of fundamental change I won't act without your prior consent. So far Andreas PS https://code.launchpad.net/~a-roehler/python-mode/string-to-syntax is still unmerged. It concerns XEmacs only (featurep 'xemacs)..., ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] simplified procedure
Hi Andreas, On Jan 11, 2011, at 09:55 AM, Andreas Röhler wrote: With respect to the still considerable amount of reports and a possible speed up of it's treatment, please permit some reflexions, how ease the process: - as for pure typos, whitespace, indent-matters IMHO developers should be permitted to push into the trunk without prior notice. Sure. I think it's fine to JFDI for trivial patches. After all, we have a version control system and post-commit notifications with diffs. I don't think you even need to do a merge proposal for those. - if funktion is changed, newly introduced, we could agree a simplified procedure, saying a delay of three days, so people may object. A merge proposal would be nice, and waiting a few days (perhaps with a ping on email or irc). Three days is probably fine, though be a little more lenient around weekends and holidays. Other than that, if you feel pretty confident about the change and no one responds, JFDI. There will be times when you might not be able to get anyone's attention for various reasons. I'd say that in the above two cases, you should not let that block your progress. Just self-approve the mp and commit. - in cases of fundamental change I won't act without your prior consent. Yep, behavior changes should require a higher barrier. A discussion on this mailing list would always be good (before, during, or after merge proposal is submitted). https://code.launchpad.net/~a-roehler/python-mode/string-to-syntax is still unmerged. It concerns XEmacs only (featurep 'xemacs)..., I commented on the mp. Cheers, -Barry P.S. Better to use my @python.org address for this mailing list. :) signature.asc Description: PGP signature ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] simplified procedure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 11.01.2011 16:20, schrieb Barry Warsaw: Hi Andreas, On Jan 11, 2011, at 09:55 AM, Andreas Röhler wrote: With respect to the still considerable amount of reports and a possible speed up of it's treatment, please permit some reflexions, how ease the process: - as for pure typos, whitespace, indent-matters IMHO developers should be permitted to push into the trunk without prior notice. Sure. I think it's fine to JFDI for trivial patches. After all, we have a version control system and post-commit notifications with diffs. I don't think you even need to do a merge proposal for those. I agree -- in fact that's what I've been doing all the time except for the new font-lock faces. - if funktion is changed, newly introduced, we could agree a simplified procedure, saying a delay of three days, so people may object. A merge proposal would be nice, and waiting a few days (perhaps with a ping on email or irc). Three days is probably fine, though be a little more lenient around weekends and holidays. Other than that, if you feel pretty confident about the change and no one responds, JFDI. There will be times when you might not be able to get anyone's attention for various reasons. I'd say that in the above two cases, you should not let that block your progress. Just self-approve the mp and commit. - in cases of fundamental change I won't act without your prior consent. Yep, behavior changes should require a higher barrier. A discussion on this mailing list would always be good (before, during, or after merge proposal is submitted). Not sure if you and Andreas agree what a fundamental change or behavior change is. Georg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk0spAQACgkQN9GcIYhpnLCeUgCbBqBC9sC2E6THsJu94miNzgxC /cEAn2B+qlEi9+ynqqpL5axqT1/KUcL5 =L/OX -END PGP SIGNATURE- ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] simplified procedure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Jan 11, 2011, at 07:40 PM, Georg Brandl wrote: -BEGIN PGP SIGNED MESSAGE- Am 11.01.2011 16:20, schrieb Barry Warsaw: Sure. I think it's fine to JFDI for trivial patches. After all, we have a version control system and post-commit notifications with diffs. I don't think you even need to do a merge proposal for those. I agree -- in fact that's what I've been doing all the time except for the new font-lock faces. Me too. Yep, behavior changes should require a higher barrier. A discussion on this mailing list would always be good (before, during, or after merge proposal is submitted). Not sure if you and Andreas agree what a fundamental change or behavior change is. Oh that's easy. If it would confuse me or Guido, it counts. :) - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJNLJkWAAoJEBJutWOnSwa/AUgP/3ThvROSuJoJkSJaZSuaX9zc 2RZM6grqDKgokLKK3xsnHFGEryJHFBL1IPxmi572FDmm2hHJII0eiR03ROfYr5bS FTN90L0aY0GbWvuJypuVGCYh3L/pGzxA9Ho6QrG3cpM18lb9q3onvlNwdOCjYtVb hTZ2+UQuCBVSk5reeDGjodk99j79CZPrI5Vucy2NnCQIhDTN9IHg5HxOSdUlu79r ivn+9LiLLdWbviNb9RVXS7cCfA6Txd3lOKjdISRAnEV+LQQ3ngaG+VI8M9xDICsw wcoblWpfkT4ntdju0otzL/hTHxR4hW53puj2b63Ictr7EFGC0AEV7mqIDtLxNvSA kLhvURDI/D+zq0cgCB0RGCIxhv0ydFfBANFB1IsIg4yyMaal7u90Kr2jHKjabnhR fg2rfFlwNT/xdF2YHO6sq9ZgNMljzcvEbh0R/z594DTYdvRpK73/og3DLERG3d5G 3g8fCurtqxzQ8RPoi3egN4s0FxZex9A9JMQcqJ//3ym/9+DlUOAFsdOnfFs2HPho f6DBWTOoPi3OD4Aicx/BjysAoaFE0fMYkmA3erwE3N/l6laLMZf8Aj6tX6N5qp10 o5VP0f3N3x2Zy6TwgqYSKZo2Q5a7OGE1CPbWom4TbwGUNilYEBWnus31rVQebLVW sBhf958bgyBG6YbTPgbb =x1ne -END PGP SIGNATURE- ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
