[jbosstools-dev] Versions bump policy change

[Max Rydahl Andersen]

On 1 Mar 2017, at 9:14, Jean-Francois Maury wrote:

> On Wed, Mar 1, 2017 at 12:16 AM, Max Rydahl Andersen 
> <manderse at redhat.com>
> wrote:
>
>> On 28 Feb 2017, at 21:42, Mickael Istria wrote:
>>
>>> On 02/28/2017 07:24 PM, Max Rydahl Andersen wrote:
>>>> sounds awesome if you guys found a way to deal with having to
>>>> manually eep these from not overlapping and avoid rerelasing
>>>> different bits with the same version number.
>>> This was:
>>> * https://issues.jboss.org/browse/JBIDE-13671
>>> * https://issues.jboss.org/browse/JBIDE-19056
>>> * https://issues.jboss.org/browse/JBIDE-22689
>>
>> none of these seem to be new ? these was what was fixe ages ago.
>>
>> So the version changes provides no benefits and becomes harder to 
>> keep
>> track on ?
>>
>> Before it could be done more or less automated. Just thought it was
>> changing because you guys found a benefit to do so.
>>
> No, just to lower the load during updates. It is now possible because 
> less
> components are being changed now (mainly OpenShift; server and base)

But that is cool.

Just curious what happens in this case:

Today I download and install latest server tools i.e. version 4.3.0

Tomorrow you release a new update to openshift tools i.e. version 3.4.1

I do check for updates - get nothing (as expected)

Next week I install into a new jboss server tools ...do I get the exact 
same bits as the one I downloaded a week ago ? or is this a new set of 
binaries just with the same 4.3.0 number ?

/max
http://about.me/maxandersen