Just curious - NoScript version numbering progression?

[anon1357]

NoScript is so functional now there doesn't seem to be any major need for an update to version 2.0 coinciding with major changes.
But it is also one of the most frequently updated programs I have ever seen.

What happens as the version number is asymptotically approaching 2.0? Do you go from 1.9.9.50 on up to 1.9.9.999 or even 1.9.9.9999?
Or start incrementing the inner numbers to more than one digit like 1.99.99.99?
Or at some point do you just arbitrarily move to 2.0?

This makes no difference to the functionality of course, but like I said, I'm curious

[Alan Baxter]

The plan has been that version 2.0 will include site-specific permissions, but apparently Giorgio's other commitments have kept him from completing it yet. Of course we want it to be pretty bullet-proof, so it may still be a while before it's ready.

It's apparent to me by now that Giorgio has a good sense of humor. Let's toss around some ideas:
- We could put together a pool, betting on how many more NoScript releases there will be before NoScript 2.0 comes out. Obviously Giorgio and members of his family would not be eligible participants. If I happened to win, however, it would definitely not be due to any inside knowledge or manipulation.
- Either of the systems you propose that asymptotically approach 2.0 should work without stressing the AMO version priority algorithm too much. I think we should give the binary number system a chance once 1.99.99 is reached. Something like:
1.99.99.1
1.99.99.10
1.99.99.11
1.99.99.100
1.99.99.101
1.99.99.110
1.99.99.111
1.99.99.1000
...

[dhouwn]

How about making NoScript 1 to NoScript 2 and NoScript 2 to NoScript 3?