Manual snapshots retention

[Tristis Oris]

@olivierlambert but on vm page it works as should.

[manilx]

@olivierlambert Now I know that there is no risk BUT it got me scared definitely. And probably will others.

Also it's just a changing of a string so it should be easy.

[olivierlambert]

Not necessarily that easy, especially on a "legacy" code base, I truly wonder if we should invest some time on this instead of XO 6?

[manilx]

@olivierlambert Your call ¯_(ツ)_/¯

[Tristis Oris]

@olivierlambert release this year? (c)

[olivierlambert]

I don't understand the question XO 6 is already here and takes 90% of our XO front team load. Anything on XO 5 will slow down the number of features available in XO 6.

[Tristis Oris]

@olivierlambert we are waiting for release)

at least it needs to be fixed in xo6.

[olivierlambert]

Waiting for what? Just add /v6 to access XO 6. The "release" is just having XO 6 by default, but it's not like "now it's available". It is already the case.

For XO 6, since it will be very different, you won't have exactly the same way of doing things than XO 5, but yes, it should be better in any way

[manilx]

@olivierlambert This feature was added not long ago anyway. Pity the text was put in this way.... The "concern" that it might scare others (did us) is valid as 99% use XO5 today.
So, perhaps you might save on support calls? My 2 cents anyway

[olivierlambert]

I will let XO PO to decide about this. Pinging @lsouai-vates

[lsouai-vates]

@olivierlambert we are thinking about implementing a relationnal DB in the future. Maybe it could offer to stock snapshots as "archived"... I don't know for now.

I understand that it could be risky to delete old snapshots, and maybe the responsability of setting the snaspshots retention can be an ACL subject...

There are plenty of avenues of work on this topic, and more generally on the retention of information about objects, tasks, and other actions. It's a real in-depth topic.