This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[db-wg] Urgent release of RIPE Database software

Previous message (by thread): [db-wg] [ncc-services-wg] Urgent release of RIPE Database software
Next message (by thread): [db-wg] More REST API Issues - /create not working

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ruediger Volk, Deutsche Telekom Technik - FMED-41.. rv at nic.dtag.de
Thu Aug 15 16:03:43 CEST 2013

Hi Job, Johan,

I'm happy to see careful attention, improvements, and tuning for
the new process.  That needs to continue and I'd expect to have some
discussion in Athens...

  > Hi,
  > 
  > Any reason not to deploy on test environmen, wait 24 hours, proceed to
  > roll out on production environment?
would seem to me: deploying the fix to the test environment would already
solve the service impact (that Johan sees) ... if we can point potential
readers of the documentation there...
So sidestepping the test environment actually delays fixing the specific
problem - while increasing risks for the production use...
My take: no need and justification for rushing change on the production system.

Kind regards,
  Ruediger


Ruediger Volk

Deutsche Telekom AG -- Internet Backbone Engineering

E-Mail:  rv at NIC.DTAG.DE

Previous message (by thread): [db-wg] [ncc-services-wg] Urgent release of RIPE Database software
Next message (by thread): [db-wg] More REST API Issues - /create not working

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]