[Info-vax] SSL V3
Jan-Erik Söderholm
jan-erik.soderholm at telia.com
Wed Feb 16 18:22:00 EST 2022
Den 2022-02-16 kl. 20:19, skrev Simon Clubley:
> On 2022-02-16, Jan-Erik Söderholm <jan-erik.soderholm at telia.com> wrote:
>>
>> It's the same as Oracle Rdb 7.4.1.1.0 being called V7.4-110 in VMS itself.
>>
>
> That's just yucky. :-)
Maybe, but it is nt a problem as such.
>
> However, that's also not something which is known by a different name
> on (say) Linux.
>
>> So, Simon, what should it be called? My understading is that there are
>> rules used by VMS on how to format a vesion number.
>
> VMS isn't the centre of the world anymore Jan-Erik.
What has that to do with internal rules for formatting a version number?
>
> Quite a lot of what VMS is running these days was written on another
> operating system and to avoid confusion on VMS, the VMS name should
> be as close to the real name as possible.
And what if that is simply no technically possible?
How much effort do you think should be put into *this* quite
made-up "problem"?
>
> If VSI make some VMS-specific changes _then_ they can call it an ECO
> or create a VMS format -release. Until then it should be the real
> version of the project that is used.
And what if that simply isn't possible?
>
> In addition to version number confusion, open source projects in
> the past have been renamed for no good reason on VMS (Apache becoming
> CSWS would be one good example). I hope VSI _never_ start doing that.
>
> Simon.
>
More information about the Info-vax
mailing list