[nebula-dev] 1.2.0 released

[Wim Jongman]

Hi All,

Congratulations! We have delivered the new Nebula release.

It is tagged here [1]
Download site is here [2]
A list with fixed bugs is here [3]

Contributors in this release are:

Jacob Filik
Johannes Faltermeier
Dirk Fauth
Donald Dunne
Morgan E. Cook
Hallvard Traetteberg
Jan "Jantje" Baeyens
Matthias P. Nowak

I thank you all!

The next release 1.3.0 [4] is scheduled for June 28, the same day as the
Oxygen Release Train.

*To the batmobile, let's go!*

Wim

[1] *https://git.eclipse.org/c/nebula/org.eclipse.nebula.git/tag/?h=1.2.0
<https://git.eclipse.org/c/nebula/org.eclipse.nebula.git/tag/?h=1.2.0>*
[2] https://eclipse.org/nebula/downloads.php
[3] https://projects.eclipse.org/projects/technology.
nebula/releases/1.2.0/bugs
[4] https://projects.eclipse.org/projects/technology.nebula/releases/1.3.0

[Dirk Fauth]

Great news! Thanks to all!

Post by Wim Jongman
Hi All,
Congratulations! We have delivered the new Nebula release.
It is tagged here [1]
Download site is here [2]
A list with fixed bugs is here [3]
Jacob Filik
Johannes Faltermeier
Dirk Fauth
Donald Dunne
Morgan E. Cook
Hallvard Traetteberg
Jan "Jantje" Baeyens
Matthias P. Nowak
I thank you all!
The next release 1.3.0 [4] is scheduled for June 28, the same day as the
Oxygen Release Train.
*To the batmobile, let's go!*
Wim
[1] *https://git.eclipse.org/c/nebula/org.eclipse.nebula.git/tag/?h=1.2.0
<https://git.eclipse.org/c/nebula/org.eclipse.nebula.git/tag/?h=1.2.0>*
[2] https://eclipse.org/nebula/downloads.php
[3] https://projects.eclipse.org/projects/technology.nebula/
releases/1.2.0/bugs
[4] https://projects.eclipse.org/projects/technology.nebula/releases/1.3.0
_______________________________________________
nebula-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

[Hallvard Trætteberg]

Well done, to all of you, and Wim deserves special thanks and credit!

From: <nebula-dev-***@eclipse.org> on behalf of Wim Jongman <***@gmail.com>
Reply-To: Nebula Dev <nebula-***@eclipse.org>
Date: Wednesday 15 March 2017 11:29
To: Nebula Dev <nebula-***@eclipse.org>
Subject: [nebula-dev] 1.2.0 released

Hi All,
Congratulations! We have delivered the new Nebula release.
It is tagged here [1]
Download site is here [2]
A list with fixed bugs is here [3]

Contributors in this release are:

Jacob Filik
Johannes Faltermeier
Dirk Fauth
Donald Dunne
Morgan E. Cook
Hallvard Traetteberg
Jan "Jantje" Baeyens
Matthias P. Nowak

I thank you all!

The next release 1.3.0 [4] is scheduled for June 28, the same day as the Oxygen Release Train.

To the batmobile, let's go!
Wim

[1] https://git.eclipse.org/c/nebula/org.eclipse.nebula.git/tag/?h=1.2.0
[2] https://eclipse.org/nebula/downloads.php
[3] https://projects.eclipse.org/projects/technology.nebula/releases/1.2.0/bugs
[4] https://projects.eclipse.org/projects/technology.nebula/releases/1.3.0

[M***@Diamond.ac.uk]

Thanks for 1.2.0, we’ve in the process of moving to it.

One thing I did notice – the version numbers in the plugins that I got from the 1.2.0 p2 site are all of the form
1.0.0.<date>
whereas I was expecting
1.2.0.<date>.

The same problem is there for what was advertised as the 1.1.0 release – version numbers that don’t match the putative contents.
This is obviously a little confusing. Did a version number bump step get missed?

Obviously this can’t be fixed for releases that have already happened, but it would be great if the version numbers for the upcoming 1.3.0 were correct.

Thanks
Matthew

From: nebula-dev-***@eclipse.org [mailto:nebula-dev-***@eclipse.org] On Behalf Of Wim Jongman
Sent: 15 March 2017 10:29
To: Nebula Dev <nebula-***@eclipse.org>
Subject: [nebula-dev] 1.2.0 released

Hi All,
Congratulations! We have delivered the new Nebula release.

[Jonah Graham]

HI Matthew,

I assume what is happening here is that the plug-ins are now Semantic
API versioned (https://wiki.eclipse.org/Version_Numbering for those
not familiar with it). That is certainly the case with the XYGraph
plug-in which released version 2.1.0 of
org.eclipse.nebula.visualization.xygraph and the 1.3.0 release of
Nebula looks like it will have 3.0.0 of that plug-in. Presumably the
plug-ins at 1.0 have had not API changes.

That said, the Eclipse platform increments the service version of
bundles on all releases[1]. That would make it possible to
differentiate bundles properly. So all bundles should be bumped from
1.0.0.qualifier to 1.0.100.qualifier for the next release.

[1] https://wiki.eclipse.org/Version_Numbering#When_to_change_the_service_segment


Jonah
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com

Thanks for 1.2.0, we’ve in the process of moving to it.
One thing I did notice – the version numbers in the plugins that I got from
the 1.2.0 p2 site are all of the form
1.0.0.<date>
whereas I was expecting
1.2.0.<date>.
The same problem is there for what was advertised as the 1.1.0 release –
version numbers that don’t match the putative contents.
This is obviously a little confusing. Did a version number bump step get missed?
Obviously this can’t be fixed for releases that have already happened, but
it would be great if the version numbers for the upcoming 1.3.0 were
correct.
Thanks
Matthew
On Behalf Of Wim Jongman
Sent: 15 March 2017 10:29
Subject: [nebula-dev] 1.2.0 released
Hi All,
Congratulations! We have delivered the new Nebula release.
--
This e-mail and any attachments may contain confidential, copyright and or
privileged material, and are for the use of the intended addressee only. If
you are not the intended addressee or an authorised recipient of the
addressee please notify us of receipt by returning the e-mail and do not
use, copy, retain, distribute or disclose the information in or attached to
the e-mail.
Any opinions expressed within this e-mail are those of the individual and
not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any
attachments are free from viruses and we cannot accept liability for any
damage which you may sustain as a result of software viruses which may be
transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England
and Wales with its registered office at Diamond House, Harwell Science and
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
_______________________________________________
nebula-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

[Jonah Graham]

So all bundles should be bumped from 1.0.0.qualifier to 1.0.100.qualifier for the next release.

BTW this is a suggestion I am making, I am not in a position on the
Nebula project to do more than make such a suggestion :-)

~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com

HI Matthew,
I assume what is happening here is that the plug-ins are now Semantic
API versioned (https://wiki.eclipse.org/Version_Numbering for those
not familiar with it). That is certainly the case with the XYGraph
plug-in which released version 2.1.0 of
org.eclipse.nebula.visualization.xygraph and the 1.3.0 release of
Nebula looks like it will have 3.0.0 of that plug-in. Presumably the
plug-ins at 1.0 have had not API changes.
That said, the Eclipse platform increments the service version of
bundles on all releases[1]. That would make it possible to
differentiate bundles properly. So all bundles should be bumped from
1.0.0.qualifier to 1.0.100.qualifier for the next release.
[1] https://wiki.eclipse.org/Version_Numbering#When_to_change_the_service_segment
Jonah
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com

Thanks for 1.2.0, we’ve in the process of moving to it.
One thing I did notice – the version numbers in the plugins that I got from
the 1.2.0 p2 site are all of the form
1.0.0.<date>
whereas I was expecting
1.2.0.<date>.
The same problem is there for what was advertised as the 1.1.0 release –
version numbers that don’t match the putative contents.
This is obviously a little confusing. Did a version number bump step get missed?
Obviously this can’t be fixed for releases that have already happened, but
it would be great if the version numbers for the upcoming 1.3.0 were
correct.
Thanks
Matthew
On Behalf Of Wim Jongman
Sent: 15 March 2017 10:29
Subject: [nebula-dev] 1.2.0 released
Hi All,
Congratulations! We have delivered the new Nebula release.
--
This e-mail and any attachments may contain confidential, copyright and or
privileged material, and are for the use of the intended addressee only. If
you are not the intended addressee or an authorised recipient of the
addressee please notify us of receipt by returning the e-mail and do not
use, copy, retain, distribute or disclose the information in or attached to
the e-mail.
Any opinions expressed within this e-mail are those of the individual and
not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any
attachments are free from viruses and we cannot accept liability for any
damage which you may sustain as a result of software viruses which may be
transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England
and Wales with its registered office at Diamond House, Harwell Science and
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
_______________________________________________
nebula-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

[Wim Jongman]

Jonah is right, we use semantic versioning. To my understanding this means:

version bumped when the API breaks
release bumped with additional features
modification/service bumped with bug fixes or other noteworthy
administration.

If none of this happened then there is no version change but only the build
date changes. Some widgets did not change from release 1.1.0 to 1.2.0 so
there are no changes in the version.

Your queue to see if you use the "right" version for those widgets is to
look at the release date.

The "Nebula Feature" gets bumped to the release number. It contains all
widgets but admittedly this is not something that people install, they only
take the ones that they really need.

Best regards,

Wim

[M***@Diamond.ac.uk]

Thanks for the explanations, Jonah and Wim, that all makes sense.

My (unnecessary) concern was not about the choice of version number (sematic versioning I am aware of), but about the mismatch between the external description (“this is release 1.2.0”) and the actual version numbers (“this release 1.0.0..”). I had completely overlooked the point that some widgets might not change from one release to another, so would not change version number.

Regards
Matthew