[Python-Dev] Sad status of Python 3.x buildbots (original) (raw)

Shorya Raj rajshorya at gmail.com
Thu Sep 4 08:59:56 CEST 2014

The limiting factor is generally time - various aspects of the current system are clumsy, but they work, so unless someone is particularly keen and willing to work through all the factors that led to the current setup and propose changes (including at least a rough concept of how ongoing maintenance will work), the status quo wins by default.

If you could outline some of these, I would be willing to have a look at what I could do.

On Thu, Sep 4, 2014 at 6:06 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:

On 4 September 2014 15:45, Shorya Raj <rajshorya at gmail.com> wrote: > Also, have you considered using Travis? It would allow us to add to the > configurations, at least generally...

Many SaaS solution assume the use of specific centralised identity providers, which isn't a function we're prepared to outsource (we know we need to fix our current proliferation of identity silos, but that's a big project and there are other tasks ahead of it on the todo list for the existing infrastructure team). The limiting factor is generally time - various aspects of the current system are clumsy, but they work, so unless someone is particularly keen and willing to work through all the factors that led to the current setup and propose changes (including at least a rough concept of how ongoing maintenance will work), the status quo wins by default. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140904/a1c904f7/attachment.html>

More information about the Python-Dev mailing list