<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="+1"><tt>Hi Tim<br>
<br>
Congratulations to you and the DB team on successfully
implementing the first big change in the DB schema and data set
for many years :)<br>
</tt></font><br>
<div class="moz-cite-prefix">On 06/05/2015 17:26, Tim Bruijnzeels
wrote:<br>
</div>
<blockquote cite="mid:499D7D01-B473-46B0-8576-3717D580974D@ripe.net"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=us-ascii">
Dear colleagues
<div class=""><br class="">
</div>
<div class="">The new attributes "created:" and "last-modified:"
have now been enabled in output.</div>
<div class=""><br class="">
</div>
<div class="">However, we found a minor bug regarding no-op
changes, that was not noticed in development or the RC
environment.</div>
<div class=""><br class="">
</div>
<div class="">If an object is submitted without any changes it
will always result in an update, because when we compare the
object the "last-modified:" value will typically not
match.(unless the update is done at sub-second speed) In other
words what should be a "no-op" now results in a "touch"
operation where only the "last-modified:" attribute is changed.</div>
</blockquote>
<br>
Just an observation. This might actually be a useful side effect. It
allows maintainers of objects to 'touch' their objects and show they
are alive and actively maintaining their data even when nothing
needs to change. I am sure some people in the community who are
going to start monitoring "last-changed:" attributes to argue that
data is out of date would appreciate that, or even request it.<br>
<br>
cheers<br>
denis<br>
<br>
<blockquote cite="mid:499D7D01-B473-46B0-8576-3717D580974D@ripe.net"
type="cite">
<div class=""><br class="">
</div>
<div class="">While this is unfortunate we do not believe that
this bug is severe enough to disable the new attributes.
Instead, we are working on a fix for this and plan to deploy
this, after thorough testing, as 1.79.2 at the end of the week.
We will also work on a retro-active fix to the history of
objects to remove those revisions of an object, where only
"last-modified:" was updated.</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Kind regards,<br class="">
<br class="">
Tim Bruijnzeels<br class="">
<br class="">
Assistant Manager Software Engineering<br class="">
RIPE NCC</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 04 May 2015, at 21:54, Tim Bruijnzeels <<a
moz-do-not-send="true" href="mailto:tim@ripe.net"
class="">tim@ripe.net</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Dear colleagues,
<div class=""><br class="">
</div>
<div class="">The batch job to add the "created:" and
"last-modified:" to all objects took longer to
complete than we anticipated (due to the higher rate
of updates in the production environment). The job was
completed late afternoon today, but since tomorrow is
a public holiday in Amsterdam we thought it better to
postpone switching on the new attributes in output
until this Wednesday to make sure we have all
engineers on board when we do this.</div>
<div class=""><br class="">
</div>
<div class="">Kind regards,</div>
<div class=""><br class="">
</div>
<div class="">Tim Bruijnzeels</div>
<div class=""><br class="">
</div>
<div class="">Assistant Manager Software Engineering<br
class="">
RIPE NCC</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On 28 Apr 2015, at 15:54, Tim
Bruijnzeels <<a moz-do-not-send="true"
href="mailto:tim@ripe.net" class="">tim@ripe.net</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Dear working group,
<div class=""><br class="">
</div>
<div class="">On 22 Apr 2015, at 11:07, Tim
Bruijnzeels <<a moz-do-not-send="true"
href="mailto:tim@ripe.net" class="">tim@ripe.net</a>>
wrote:
<div class="">
<blockquote type="cite" class="">
<div class=""><span class="">Because no
major changes were introduced with
these fixes we plan to adhere to the
original planning and deploy the
1.79.1 release of whois to the
production environment on Tuesday 28
April (Monday is a public holiday
here), and we plan to enable the new
attributes in the output on Monday 4
May.</span></div>
</blockquote>
</div>
<br class="">
</div>
<div class="">We have deployed 1.79.1 to
production today.</div>
<div class=""><br class="">
</div>
<div class="">We are currently running the
updates to generate the values for
'last-modified:' and 'created:' in the
background and plan to enable these new
attributes in output Monday 4 May - because
the background job needs some time to
complete, and we prefer not make changes
like this too close to the weekend.</div>
<div class=""><br class="">
</div>
<div class="">Kind regards,</div>
<div class=""><br class="">
</div>
<div class="">Tim Bruijnzeels</div>
<div class=""><br class="">
Assistant Manager Software Engineering<br
class="">
RIPE NCC</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</blockquote>
<br>
</body>
</html>