That is probably close to the actual way it works, but not quite equal. My
mental model when making this went backwards in time, towards 0, not
forwards.
It's something like this (using the numbers from your first example): make
a bucket of the specified "timeUnit" size (1000), that contains the "
So there is no reason for an end-user to actually use 3.1, because it will
have the same features as 3.0.x, but won't be maintained? 3.0.x for high x
will be 3.1 plus more bug fixes. I'm not saying that's bad. Starting from
3.2, using any subsequent version will make sense.
On Tue, Nov 10, 2015 at
