Caraya User Survey

[jimkring]

Please see this survey. We'd love your feedback:

https://jimkring.typeform.com/to/qrZIeh

CC'ing active contributors and users: @omarmussa @francois-normandin @JKISoftware/jki-staff @neilpate @OlivierLabo @kosist @drjdpowell @StefanD986 @volks73

[OlivierLabo]

Hi Jim,

I took the survey this morning, but I realize that I forgot a particular point, about versioning.

When I have a look in VIPM for last updates of Caraya, I see several versions (0.6.0.49; 0.6.1.51; 0.6.3.54) with the same Release Notes. So I don't know the differences between 0.6.0.49 & the last 0.6.3.54.

Regards,

Olivier

[jimkring]

@OlivierLabo thanks for mentioning the release notes. For the past few minor releases, we've been appending the new features/fixes to the bottom of the lists. See here for an example: 0.6.3. This doesn't work so great for the release notes in VIPM, and I agree it would be good if we only included what's new for that release.

[francois-normandin]

I'm the culprit. I had decided to extend the release notes until we updated the Minor build number. My reasoning was that while we are in 0.6.x.x, we are really in the same released version. The third digit being for "Fixes", that's why I simply appended the release notes.

(I will conform to VIPM release note pattern next time)

[jimkring]

@francois-normandin @OlivierLabo for what it's worth, I'd love to have a nice/better/structured way of tracking release notes in software releases. It seems that VIPM could do an even better job of this, but that's a separate topic :-)