libusbx versioning (was Re: [Libusbx-devel] Keeping the 1.0.9rc3 tag)

[Pete Batard]

I should also add that the process as I currently see it, is designed to 
freeze the version the precise moment someone creates a fork off 
mainline, precisely because it relies on a precommit hook that needs to 
be manually setup (and that people who aren't mainline committers would 
therefore not set up, especially if we make the fact that it's internal 
explicit in the script itself).

Thus, from the moment a contributor decides to work on their own branch, 
the version will remain frozen to the point in mainline that identifies 
UNIQUELY where they forked, which gives us all the information we need 
to know. Whatever they add on top is not something we want to look at 
unless they feed it back to us for integration, in which case, if 
approved, it gets back into our versioning scheme.

Somehow I am under the impression that you would like libusbx's 
versioning to also solve the versioning of anybody who creates a fork, 
so that we can then support people coming with "hey, I created a custom 
version of libusbx and added/removed stuff on my own that you will have 
to figure out - please support it".

Unless we decide to officialize a fork, with an offset (or something 
else), in case that fork is going to see semi-official releases, I don't 
really see solving versioning of custom branches we know nothing about 
as part of our mandate.

Now, unless you (or anybody else) have an actual counter proposal which 
they think is better with regards to versioning, and that they can 
demonstrate to this list, none of this discussion is going to do much to 
*solve* the problem. Thus, if you think there's a better way, please 
have something to show for it that we can check out.

Regards,

/Pete