Petascope version number

[Vlad Merticariu]

Set petascope version number to rasdaman version.

[Dimitar Misev]

Please specify component/milestone and other details when creating tickets.

[Bang Pham Huu]

From my view, Petascope is separating with Rasdaman and only update to new version if there are a lot of significant changes also (but it is up to you to do this).

[Dimitar Misev]

Where is this petascope version mentioned/maintained btw?

[Bang Pham Huu]

Vlad, could you suggest something about this ticket?

[Vlad Merticariu]

We don't have an established release procedure for separate components. Establishing one would help decoupling, but I don't see how this is possible when keeping all of them in the same repository.

As far as they stay in the same repo I don't think there is any other indicator of the current version, other than the rasdaman version tag.

Opinions?

[Peter Baumann]

we have used petascope version numbers in the past, but not coherently. IMHO this is just complicating things for users and dev'ers. For both reasons I opt for KISS = one comprehensive version.

[Dimitar Misev]

+1

[Dimitar Misev]

I think the idea of this ticket was, on startup petascope reports some version (which is set in petascope.properties??). It should instead report the output of rasql select version()

[Bang Pham Huu]

Ok, I will wait Vlad's confirmation the idea of Dimitar before starting do it (thanks Dimitar).

[Bang Pham Huu]

@Vlad: Dimitar's idea is what you want to have? Please confirm and this could help me.

[Vlad Merticariu]

Yes, that is right, petascope should report rasdaman version at startup.

[Bang Pham Huu]

the patch was accepted, thanks, close ticket here.