But adding something that was not there before is just the same thing. If I
have a topology that is using guava, and storm adds in a dependency with a
different version to the classpath without shading it, I just broke that
topology.
- Bobby
On Wednesday, May 18, 2016 2:26 PM, P. Taylor Goetz <ptgo...@gmail.com>
wrote:
On May 18, 2016, at 2:46 PM, Bobby Evans <ev...@yahoo-inc.com.INVALID> wrote:
If this is for 1.x then we might want to go to 1.1, not sure what the policy is
for adding something new to the classpath.
- Bobby
There was a discussion thread around this. My feeling is that for 1.x, since we
are adding APIs we should bump the minor version (i.e. 1.1.x).
I don’t think adding something to the classpath warrants a minor version bump
unless it adds something to a *Storm* API.
-Taylor
