Re: [Python-Dev] Where is our official policy of what platforms we do support?
On Thu, 15 May 2014 19:14:55 +0200, Antoine Pitrou wrote: > On Thu, 15 May 2014 09:40:33 -0500 > Skip Montanaro wrote: > > On Thu, May 15, 2014 at 9:35 AM, Brett Cannon wrote: > > > I view stable buildbots as staying up and testing critical platforms. > > > > Would "supported" and "unsupported" (or "critical" and "optional"?) > > make more sense? "Unstable" suggests "broken" to me, not "we don't > > really care about these." > > I don't know who came up with these names in the first place. > However there's a slight nuance here: some platform may be supported, > but still some buildbot end up in the "unstable" category if it has > issues of its own (for example the machine has a flaky network > connection, etc.). And indeed there are Linux and Windows machines in > the "unstable" category. There's also nothing stopping us from putting a "niche platform" buildbot into the stable group if it normally builds fine. I suppose it would be pretty much supported by default then, though, if it being red was a release blocker. But we could decide to ignore a red 'niche' buildbot at release time; so, I think 'stable' vs 'unstable' is indeed the most descriptive: unstable buildbots are the ones that turn red "randomly"[*], or are always red because no one has fixed whatever the problem is (which might be on the buildbot or in our code). --David [*] Yes, our stable platforms do that sometimes too, but those are test instabilities, whereas unstable buildbots fail tests other than the known unstable tests. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Where is our official policy of what platforms we do support?
On Thu, 15 May 2014 09:40:33 -0500 Skip Montanaro wrote: > On Thu, May 15, 2014 at 9:35 AM, Brett Cannon wrote: > > I view stable buildbots as staying up and testing critical platforms. > > Would "supported" and "unsupported" (or "critical" and "optional"?) > make more sense? "Unstable" suggests "broken" to me, not "we don't > really care about these." I don't know who came up with these names in the first place. However there's a slight nuance here: some platform may be supported, but still some buildbot end up in the "unstable" category if it has issues of its own (for example the machine has a flaky network connection, etc.). And indeed there are Linux and Windows machines in the "unstable" category. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Where is our official policy of what platforms we do support?
On Thu, May 15, 2014 at 9:35 AM, Brett Cannon wrote: > I view stable buildbots as staying up and testing critical platforms. Would "supported" and "unsupported" (or "critical" and "optional"?) make more sense? "Unstable" suggests "broken" to me, not "we don't really care about these." S ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Where is our official policy of what platforms we do support?
On Thu May 15 2014 at 10:24:45 AM, Skip Montanaro wrote: > On Thu, May 15, 2014 at 8:26 AM, Antoine Pitrou > wrote: > > We already have such buildbots, they are in the "unstable" category. > > You can browse through existing buildbots here: > > https://www.python.org/dev/buildbot/ > > I can't see how to distinguish "stable" from "unstable" (or to view > just the "unstable" category. Take http://buildbot.python.org/all/waterfall?category=3.x.stable&category=3.x.unstableand remove the category GET argument that you don't want to see, e.g. to only see unstable buildbots use http://buildbot.python.org/all/waterfall?category=3.x.unstable > What do those two categories have to do > with "supported" and "unsupported"? > Antoine can give the definitive answer, but I view stable buildbots as staying up and testing critical platforms. I.e. when I submit a patch I make sure the stable buildbots are always green (unless it's a transient failure) and I don't worry about the unstable ones (I view them as more informative than necessary). Basically red stable buildbot should block a release. -Brett ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Where is our official policy of what platforms we do support?
On Thu, May 15, 2014 at 8:26 AM, Antoine Pitrou wrote: > We already have such buildbots, they are in the "unstable" category. > You can browse through existing buildbots here: > https://www.python.org/dev/buildbot/ I can't see how to distinguish "stable" from "unstable" (or to view just the "unstable" category. What do those two categories have to do with "supported" and "unsupported"? Skip ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Where is our official policy of what platforms we do support?
On Thu, 15 May 2014 08:20:03 -0500 Skip Montanaro wrote: > On Wed, May 14, 2014 at 11:05 PM, Guido van Rossum wrote: > > Main problem with rare platform support is not breaking it accidentally, > > since without buildbots we won't know when it's broken. This is why we don't > > make any promises. > > Should we (or do we) offer to run (unofficial) buildbots for > maintainers of minority platforms where possible? For example, I have > no idea if a buildbot for MirOS is even feasible, but if the guy who > submitted the patch is amenable and it is possible to run a buildbot > slave for that OS, it still might be useful to have a "one stop" place > for this. If failing, such buildbots wouldn't block a release, but > would still provide tools for people to track down the source of > breakage. We already have such buildbots, they are in the "unstable" category. You can browse through existing buildbots here: https://www.python.org/dev/buildbot/ In the case of MirOS, though, I'm unsure core developers would proactively fix failures on such a niche platform :-) Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Where is our official policy of what platforms we do support?
On Wed, May 14, 2014 at 11:05 PM, Guido van Rossum wrote: > Main problem with rare platform support is not breaking it accidentally, > since without buildbots we won't know when it's broken. This is why we don't > make any promises. Should we (or do we) offer to run (unofficial) buildbots for maintainers of minority platforms where possible? For example, I have no idea if a buildbot for MirOS is even feasible, but if the guy who submitted the patch is amenable and it is possible to run a buildbot slave for that OS, it still might be useful to have a "one stop" place for this. If failing, such buildbots wouldn't block a release, but would still provide tools for people to track down the source of breakage. Skip ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Summary of Python tracker Issues
Hi, On Sat, Feb 8, 2014 at 1:37 PM, francis wrote: > On 02/07/2014 06:07 PM, Python tracker wrote: >> >> Open issues with patches: 2045 > > > Has somebody done a graphic of that data againsttime? > You can find some charts here (it's still a work in progress though): http://bugs.python.org/issue?@template=stats Best Regards, Ezio Melotti > Regards, > francis > ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
