bigtop releases and minor/patch versioning

[na...@reactor8.com]

In looking over the 0.9 BOM jira and tracking the list more recently about
updates and release work ongoing wanted to get sense of what the group
thoughts are on versioning and what it means in bigtop to have a patch and
minor release.

 

Looks like group has 0.9 in its crosshairs to push to completion then
turning towards 1.0.  If looking at from semver style, has group discussed
in past doing patch versioning to do minor revs on components?

 

Example would be the 0.9 jira started in Oct, since then two versions of
spark have rolled through with already an update patch ready for spark 1.1
for 0.9.  Could bigtop look towards idea of cutting a 0.8.1 patch for
instance that would rev only the spark component and get it out the door as
quick as possible so as to be as up to date with components and getting in
people's hands as quick as possible.

 

If people don't like the idea of using patch number for something like
revving component.., maybe better to just bump bigtop straight to 1.0
next.., then conceptually would just do "minor" patch (ie: example of bigtop
1.0 with component 0.5 , and bigtop 1.1 with component 0.6).  This might be
appealing as I could see then patch versioning being leveraged for things
like added/fixed/enhanced tests