Warzone 2100 Forums

Emdek wrote:The best solution would to but warning: "this is beta stuff, it can eat your cat, but we would appreciate feedback anyway".

I double dare them to write that in the next beta 7 I mean beta 8!
nobody ever said why beta 3 was pulled

I guess because of similar issues, but found in time before making it public.
It got tagged AFAIK so it needed to be skipped.

zany wrote:nobody ever said why beta 3 was pulled

Hm, that one... iirc think after tagging beta3 there were some... irregularities found in network games nobody could reproduce later and a commit that might or might not help or be necessary; until deciding to include that enough time passed that redoing the beta3 tag might leave some people with the old one, so we made a new one.

cybersphinx wrote:

zany wrote:nobody ever said why beta 3 was pulled

Hm, that one... iirc think after tagging beta3 there were some... irregularities found in network games nobody could reproduce later and a commit that might or might not help or be necessary; until deciding to include that enough time passed that redoing the beta3 tag might leave some people with the old one, so we made a new one.

tagging is what? mark it for release and that can't change?

zany wrote:tagging is what? mark it for release and that can't change?

Basically, yes. A static name for one commit. You can make that point to another commit, but if someone already got the old one, it won't automatically update. See also "On Re-tagging" here: http://schacon.github.com/git/git-tag.html

zany wrote:

Emdek wrote:The best solution would to but warning: "this is beta stuff, it can eat your cat, but we would appreciate feedback anyway".

I double dare them to write that in the next beta 7 I mean beta 8!
nobody ever said why beta 3 was pulled

they didn't do it

Emdek wrote:The best solution would to but warning: "this is beta stuff, it can eat your cat, but we would appreciate feedback anyway".

It can't do that (unless you didn't follow all of the recommended safety instructions exactly).

What about:

"This is a beta release. If you use it we will rob your dog and sell it back to you. We know where you live. That is all."

Cyp wrote:

Emdek wrote:The best solution would to but warning: "this is beta stuff, it can eat your cat, but we would appreciate feedback anyway".

It can't do that (unless you didn't follow all of the recommended safety instructions exactly).

I was thinking so, but someone reported that such thing happened, I couldn't believe it, but well, strange things happen.

well, you could just tell the cry babies that the next release will be an alpha instead of a beta. Then we shall see if they cry over the next beta or not