yeti_c wrote:... about upgrades and testing...
And I've come up with a plan... And this only works for 3.6.x +.
OK - I will code up and release BOB in here and on userscripts... so the people that pay attention to this thread can download the new code whenever it's available...
Then, say, a day later - I will upgrade the BOB support script with the new version number(s)...
This will then inform people that there is an upgrade available that's been tested (a bit).
Now this doesn't guarantee that BOB will be tested when it's upgraded... but it will help.
So what I need from you regular commenter guys... is whenever a new BOB is released in here then download it - give it a go and get back to me with feedback... if no feedback - then I will release it to the public...
OK. Good thoughts yeti.
I think this is a cool idea in concept. However I think it needs more structure to work well primarily for the good of the script and secondarily for the good of the "public/casual users".
version numbering
Yeti_c's version numbering is in the form X.Y.Z where ...
X is a major version [1 was stocksr's script, 2 was yeti_c's AJAX compatible version, 3 was to address CC's update to allow 8 player games.]
Y is a new feature version [3.3 was Deferred Armies and Last Bonus added to the stats table, 3.4 was Hide Menu.]
Z is the bug fix version.
Keeping yeti_c's preferred way of working (ie rapid implementation and publishing of new ideas and code) I suggest the following slight modifications:
(i) Append .0 or .1 to this existing format of version number. .1 for stable/fixed/alpha versions and .0 for potentially unstable/broken/beta versions.
This is required because there is no way of knowing from the version number if it is stable/fixed/alpha or not. 3.3.2 and 3.4.5 were the stable/alpha versions of the new feature versions mentioned above.
So 3.4.1, 3.4.2, 3.4.3, 3.4.4 and 3.4.5 would have been published as: 3.4.1.0, 3.4.2.0, 3.4.3.0, 3.4.4.0 and 3.4.5.0
and then 3.4.5.1.
(ii) yeti_c to set up another userscripts.org page. The current page to be used for the beta versions and the new page used for alpha versions.
(iii) BOB to be modified to include the following feature:
Update Notification: alpha | beta | off.
I think it will be clear to all followers of this thread how this feature would work and that it would address all the issues raised by (effectively) getting the whole community to bug/beta test BOB as has been happening recently.
development cycle
Much the same as now. However I do think that it would be useful if we discussed proposed new features and possible implementations of them
at greater length in this thread before yeti_c implements them. If the followers of the thread agree that a feature is unnecessary it can save time for yeti_c to do the stuff we all agree we do want

. For emphasis I am in no way suggesting that yeti_c
has to do the will of the thread - see the Cicero's Five Golden Rules of BOB Appreciation in a previous post
I'll stop there before I get fast posted.
Cicero