[db-wg] Database release 1.79.1 deployed to RC environment

Hi all,

On Thu, May 07, 2015 at 09:55:25AM +0200, Tim Bruijnzeels wrote:
> > On 06 May 2015, at 18:14, denis <ripedenis at yahoo.co.uk> wrote:
> >> If an object is submitted without any changes it will always result
> >> in an update, 

I had a similar bug in one of our (AS8283) provisioning scripts :-)

> > 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 
> 
> Sure, there is something to be said for this, but the downside of this
> is that the version history of the object becomes very large, which
> may not be desired.

It would be a ton of signalling, but for what purpose? Some objects are
perfectly fine for years on end without change. A better, less
obtrusive, keepalive mechanism are the invoices that RIPE NCC sends to
its members. At the moment there is no requirement to demonstrate to
others you have a script running that can touch all objects.

> As far as I know this was not explicitly specified beforehand, so it
> would be good to have a clear WG consensus call on this now.

When (if ever) such a request comes to the DBWG we will discuss it
accordingly.

> For the moment we feel that it's probably best to apply the planned
> 'fix' because the behaviour will then be consistent with no-ops until
> now, but we can always revert this change when we get a clear
> direction from the WG.

Implementing the bugfix is the correct course of action. At the moment
the behaviour is not as expected and I appreciate the NCC taking action
on such short notice.

Kind regards,

Job