<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">That seems like a reasonable approach
to me.<br>
<div class="moz-signature"><br>
<span style="font-family: Arial;">
Tim Garrison<br>
Software Engineer III<br>
<br>
<b>SoftLayer, an IBM Company</b><br>
315 Capitol Street Suite 205, Houston, TX 77002<br>
281.714.4213 direct | 713.540.4325 mobile | 281.714.4657 fax |
<a class="moz-txt-link-abbreviated" href="mailto:tgarrison@softlayer.com">tgarrison@softlayer.com</a>
</span><br>
<br>
</div>
On 08/15/2013 08:32 AM, Job Snijders wrote:<br>
</div>
<blockquote
cite="mid:D7DDBFC2-F27E-4BD3-9755-D636033C7483@atrato.com"
type="cite">
<pre wrap="">Hi,
Any reason not to deploy on test environmen, wait 24 hours, proceed to roll out on production environment?
Kind regards,
Job
On Aug 15, 2013, at 3:27 PM, Johan Åhlén <a class="moz-txt-link-rfc2396E" href="mailto:jahlen@ripe.net"><jahlen@ripe.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Dear Ruediger,
Thank you for the input. As you are all aware the release procedure is new and does require some tuning, so in that aspect any suggestions on how we can improve this are welcome.
In this particular situation our assessment is that the broken links in the documentation indeed has a service impact. For some users this could be critical as they may not be able to use the REST API service. At least one case was reported to us where the development towards the API has come to a halt because of this.
Perhaps in this case we can hold the deployment of the fix until the working group advices us on how to proceed.
Kind regards,
Johan Åhlén
Assistant Database Manager
RIPE NCC
On 15 Aug 2013, at 14:52, "Ruediger Volk, Deutsche Telekom Technik - FMED-41.." <a class="moz-txt-link-rfc2396E" href="mailto:rv@NIC.DTAG.DE"><rv@NIC.DTAG.DE></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Dear Johan,
thanks a lot for the new much more transparent mode of software
version management for the RIPE data base service.
This is a huge improvement.
Nevertheless I think that we need continued discussion in the community to
improve mutual understanding of considerations and impact.
Your message today brings up few consideratiosn from me
(a bit more tuned to the general pro cess than the specific case).
</pre>
<blockquote type="cite">
<pre wrap="">We were recently made aware of some issues with the documentation
related to the REST API. To fix these issues requires a new release of
the Database software as some parts of the documentation are generated
from the active code. The documentation is vital for anyone wanting to
use the service. We therefore believe it is necessary to make a new
release containing this fix only and deploy it directly to production
later today.
</pre>
</blockquote>
<pre wrap="">The problem description does NOT read like there IS ACTUAL SERVICE IMPACT
at the moment; looking at the RIPE NCC service status page seems to confirm
since it reports "no known problems" and no ser vice announcements either.
Doing a software version change with less than a day advance notice certainly
can be appropriate as an "emergency update" to deal with some service impact.
How much harm is done if fix to the documentation is done a few days later
while a note is posted indicating that certain errors will be fixed
in the near future... ?
</pre>
<blockquote type="cite">
<pre wrap="">In this particular case we don=92t believe it is necessary to put the
release in test beforehand. The only fix is for the documentation and
this is preventing users form using the service, so it's quite urgent.
This fix should have no impact on any other part of the RIPE Database
service.
</pre>
</blockquote>
<pre wrap="">I am tempted to believe your assessment; I dont have access to the changes
and the resources to do my own full assessment.
As I did experience 3 service impacting bugs within 12 months with
UNannounced version changes I conclude that I rather see than believe.
I certainly do see a need to watch more carefully how software behaves
after ANY change and a non zero probability of some surprise
(that could result in service impact for me).
Note: knowing the schedule of upcoming changes some time in advance
can be more important than actually having the ability to run tests
(like due to IETF timing I could not run tests against the test server with
1.67.4 - but we did schedule preparation of critical production runs in
a way that protected us against potential surprises due to the software change.)
</pre>
<blockquote type="cite">
<pre wrap="">If you have any questions then please let us know.
Kind regards,
Johan =C5hl=E9n
Assistant Manager Database
RIPE NCC=
</pre>
</blockquote>
<pre wrap="">Best regards,
Ruediger
Ruediger Volk
Deutsche Telekom AG -- Internet Backbone Engineering
E-Mail: <a class="moz-txt-link-abbreviated" href="mailto:rv@NIC.DTAG.DE">rv@NIC.DTAG.DE</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<br>
</body>
</html>