View Issue Details

IDProjectCategoryView StatusLast Update
0005003SUMoNew Featurepublic2019-05-19 09:52
Reporterdemos Assigned ToKyle_Katarn  
PrioritynormalSeverityminorReproducibilityhave not tried
Status acknowledgedResolutionopen 
Product Version5.7 
Target VersionLong term 
Summary0005003: Add info about update date
DescriptionIt will be useful if you add in SUMo solumn with date where this update released or published or added to your db.
TagsNo tags attached.

Activities

wolf

2019-05-16 22:17

reporter   ~0003309

On SUMo client side, I'm interested too to know the date of release. And yes there are well known examples where it is difficult to determine the release date, i.e. the chaos created by Microsoft for its Windows operating system update 1809 of Windows 10. As far as I've read the latest notes by Microsoft, the release date has been reassigned of some date in October 2018 to some date in November 2018. And this doesn't coincide with publishing, roll-out or public availability which depended on the kind of update service in use by the customer varying of start rollout by mid-November 2018 unto end of March 2019.

On SUMo server side, it might be interesting when a version has been added to the SUMo server database of software tools detected by SUMo clients.

Kyle_Katarn

2019-05-16 22:21

administrator   ~0003310

This is currently not technically possible because of the way SUMo server "dynamically computes" current version number. However, I understand the request and i'll investigate if I can find a reliable way to do it.

wolf

2019-05-16 23:00

reporter   ~0003315

One way requires quite some refactoring including change in protocol. Instead of considering consolidated tool name and its version as a signature value it should be replaced by considering it a vector. Then consolidated tool name, version and bit edition can just be components of such a vector and can be added by tool edition and operating system just to name the most relevant dependency factors resp. dimensions. Then there may be various versions of a tool be current as there are already various versions in state beta, depending on this vector resp. ignoring components for this determination. Switching of current signature consideration to more complex vector consideration may be a transition before changing the determination of current.

demos

2019-05-17 07:31

reporter   ~0003317

About difficulty to determine the release date. As for me I try to find release date from official site news or changelogs. If there is no such info, I see if file is digitally signed. If it is then I use the date of signing.

Kyle_Katarn

2019-05-18 12:15

administrator   ~0003340

I'd prefer to avoid manual action to set these dates. I'd better look for automatic computation on server side, along with detection of most up to date version. therefore it's a complex, long term item.

demos

2019-05-18 19:33

reporter  

SUMo.png (23,373 bytes)   
SUMo.png (23,373 bytes)   

demos

2019-05-18 19:33

reporter   ~0003341

Then I repeat that in many cases you can do it automatically by using the date of signing. In other cases may be the last modified date value could be used.

Kyle_Katarn

2019-05-19 09:52

administrator   ~0003342

Yes, i agree, but this require an adaptation of the client/server protocol.

Issue History

Date Modified Username Field Change
2018-07-05 11:07 demos New Issue
2018-07-05 21:32 Kyle_Katarn Assigned To => Kyle_Katarn
2018-07-05 21:32 Kyle_Katarn Status new => acknowledged
2018-07-05 21:32 Kyle_Katarn Target Version => Long term
2019-05-16 22:17 wolf Note Added: 0003309
2019-05-16 22:21 Kyle_Katarn Note Added: 0003310
2019-05-16 23:00 wolf Note Added: 0003315
2019-05-17 07:31 demos Note Added: 0003317
2019-05-18 12:15 Kyle_Katarn Note Added: 0003340
2019-05-18 19:33 demos File Added: SUMo.png
2019-05-18 19:33 demos Note Added: 0003341
2019-05-19 09:52 Kyle_Katarn Note Added: 0003342