Use case
The reason I’m posting this here is 8.3 no longer shows the module description as a column. That means the customer/user must mouse over the module to see the full version, once we start releasing service packs. It seems like it will be very easy to miss modules of incompatiable versions.
Request
Sepasoft has both RC’s and SP’s (service packs). The ‘rc’ string in the version is valid (as are ‘alpha’ and ‘beta’), however, ‘sp’ is not valid. So users must mouse over the module to see the service pack number. Please add ‘sp’ as a valid alpha in the version (xx.yy.zz-sp1).
I posted this on the IDEAS website also, since the beta is complete.
Thanks.
I think there’s very little chance we’ll be mucking around with the versioning, especially at this point, but maybe there’s something we can do on the modules page to make things better.
Can you add some screenshots to show what you’re dealing with now?
Thanks Kevin. I knew it was a longshot this late.
The underlined ‘rc’ in the screenshot is what I’m talking about. I know the description can be added to the table, but it would be quicker for a user or Sepasoft support to know which version they are running. When we go from an RC to stable we start using Service Pack as our 4th segment. It would be helpful to be able to turn that ‘rc1’ into an ‘sp1’, ‘sp2’ etc.
Hope this is helpful to others, including IA. Thanks.
