3.1 Beta reminder

The projects speaking tube.
Add your two cents if you want to.

3.1 Beta reminder

Postby Staff » 01 Mar 2012, 05:02

I would like to clarify a few things about how these beta builds work.

We are trying to fix all major bugs as we, and you, the users, find them, and as time allows. In order to do this, we must be able to replicate the issue, and without a good way to replicate it, it is a big (time-consuming) guessing game.

This means that we need every bit of information that you can supply us, as well as crash report files and or savegames, so we can fix as many bugs as possible before the release of 3.1.0.

Here are the locations of the crash report files, and savegames, as well as anything else. FileLocations#Crashdumps
  • All bugs should be reported here: http://developer.wz2100.net/newticket.
    Don't make the mistake that someone else will report the issue, usually, people don't report it, or they don't give enough information to replicate the issue.
  • You can search for the same kind of bug you have, and there might be a ticket that is closed with the "need info" response. That means we don't have enough information to replicate the issue at hand. Feel free to add information to that ticket, so we can all debug what is going on, and hopefully solve the issue.
  • Feel free to add relevant information to open tickets as well, but adding a "me too" response does nothing to help us. We need to find a way to replicate the issue.

Warzone 2100 can't cause your system to crash. It does not have kernel level access.
When your system crashes (reboots on windows / or a BSOD) that is the result of video drivers, or perhaps sound, it can also be because your system is unstable.
  • The way to check for system stability is to run memtest86+ (free) http://www.memtest.org, and you can install that onto a USB flash drive. Then once that is done, let it run overnight, and hopefully you will have 0 errors. If you have errors, that means your RAM needs replacing, or the timings are set incorrectly.
  • Another tool (windows only) for testing for CPU/heat issues is http://www.ocbase.com/perestroika_en/index.php?Download it is also free. You only need to run this for 1-2 hours, and usually, that is enough to see if your CPU is stable or not.
  • Another popular tester is prime95, (free, for Windows, Mac OS and Linux), get it here: http://www.mersenne.org/freesoft/
You should try newer (and sometimes older) video/sound drivers, since those also have bugs, once you verify that the issue is with the video drivers, and not system stability.
User avatar
Staff
Global Moderator
Global Moderator
 
Posts: 361
Joined: 27 May 2011, 03:08

Re: 3.1 Beta reminder

Postby Staff » 01 Mar 2012, 05:02

Here are the tickets that we have that are still open for the 3.1 beta line.
http://developer.wz2100.net/report/17

Please help us figure out how to replicate these, so we can fix them. :3
User avatar
Staff
Global Moderator
Global Moderator
 
Posts: 361
Joined: 27 May 2011, 03:08

Re: 3.1 Beta reminder

Postby vexed » 01 Mar 2012, 05:03

*Reserved*
/facepalm ...Grinch stole Warzone🙈🙉🙊
User avatar
vexed
Inactive
Inactive
 
Posts: 1518
Joined: 27 Jul 2010, 01:07

Re: 3.1 Beta reminder

Postby cybersphinx » 01 Mar 2012, 18:22

http://en.wikipedia.org/wiki/Software_release_life_cycle#Stages_of_development
http://en.wikipedia.org/wiki/Software_testing#Objectives_of_testing
The pre-alpha and alpha part applies to the development branch called "master" (which is not a release, will never be a release, and will keep changing).
"Alpha software can be unstable and could cause crashes or data loss."
"Regression testing focuses on finding defects after a major code change has occurred. Specifically, it seeks to uncover software regressions, or old bugs that have come back. Such regressions occur whenever software functionality that was previously working correctly stops working as intended. Typically, regressions occur as an unintended consequence of program changes, when the newly developed part of the software collides with the previously existing code."
This is where viewtopic.php?p=95146#p95146 comes in (callgraph of the Warzone code or whatever it is exactly), that might give you an idea how difficult it is to change something without breaking anything else. The problem of how to find those regressions leads us to...

http://www.catb.org/~esr/writings/cathe ... al-bazaar/
"Release early. Release often. And listen to your customers."
Now before you complain about the "listen to your customers" part, have a look at http://www.ohloh.net/p/warzone2100/analyses/latest and http://www.ohloh.net/p/blender/analyses/latest - both projects have a codebase of roughly a million lines according to Ohloh. But the "Commit Volume" over the past twelve months shows 9 named contributors and 22% others for Blender (whose associated Blender Foundation regularly sponsors projects to improve it: http://en.wikipedia.org/wiki/Blender_Fo ... n_Projects), while Warzone has five named contributors (of which dak180 doesn't touch code, only the Mac build system) and 13% others (who all do this in their spare time). The problem is less with listening, than with finding the time to actually do something about it.

Also, this essay was written when customers/users of free software were much more likely to become contributors/developers.

https://lwn.net/Articles/482557/
"[...] projects are making their own decisions, freely, based on their interests and understanding of the problems they are solving. No one has set out to annoy anyone. That may be a side effect of the changes that are being made, but it certainly isn't the intent.
[...] they clearly see them as improvements. It's a little hard to imagine that folks would spend significant amounts of their time making the code worse. Opinions will differ on the changes, of course, and making one's opinion known is a time-honored tradition in free software (not to mention the internet and human society in general). But the vehement, sometimes demanding, tone that those complaints take is counter-productive. Part of what seems to be lacking is a certain of level of respect for the projects and the people behind them.

A much more effective way to make one's opinion known is through engagement. Unlike the proprietary world, we in the free software world can directly engage with the developers"

viewtopic.php?f=30&t=6430 (2010-09-11)
http://developer.wz2100.net/ticket/3135 (2012-02-07)
https://github.com/Warzone2100/warzone2 ... 58a987b1a4 (2012-02-10)
We want information... information... information.
cybersphinx
Inactive
Inactive
 
Posts: 1588
Joined: 01 Sep 2006, 18:17

Re: 3.1 Beta reminder

Postby kilroy9724 » 02 Mar 2012, 22:38

boys to me the game after 5 minutes that I was starting a skirmish crashed.
I also tried to delete the old files for version 2.3.9 but went anyway .........
Any idea? :hmm: :hmm: :hmm: :hmm:
kilroy9724
New user
 
Posts: 5
Joined: 25 Feb 2012, 19:17

Re: 3.1 Beta reminder

Postby Searge-Major » 03 Mar 2012, 00:42

cybersphinx wrote:...have a look at http://www.ohloh.net/p/warzone2100/analyses/latest ....



:shock: Warzone is worth 12.8 million dollars... :shok:

:yahoo: :biggrin1:


As for the rest, well, I've always tried to be respectful of everyone, especially the devs. :3

But my apologies if in reporting any problem I've had, I committed one of those cardinal sins... :oops:

Btw, thanks for a great project. :wink:
I fully realise my input is just another drop in the proverbial bucket. It is my goal to make each drop count.
Searge-Major
Trained
Trained
 
Posts: 182
Joined: 10 Sep 2011, 02:36
Location: Great Southern region, Western Australia

Re: 3.1 Beta reminder

Postby NoQ » 08 Mar 2012, 14:32

Suppose there is a bug ticket that has been submitted long time ago and already forgotten but still relevant, and i just found something hopefully-interesting that might help in investigating and fixing it quickly (well, anything is possible lol). If i just post a message into the ticket's discussion, will anybody notice that? I'm asking because it doesn't appear on the timeline.
User avatar
NoQ
Elite
Elite
 
Posts: 5613
Joined: 24 Dec 2009, 10:35
Location: /var/zone

Re: 3.1 Beta reminder

Postby cybersphinx » 08 Mar 2012, 14:37

NoQ wrote:If i just post a message into the ticket's discussion, will anybody notice that?
Any ticket change is announced in #warzone2100-dev, and emailed to anyone who posted in the ticket. The timeline should have them as well though iirc.
We want information... information... information.
cybersphinx
Inactive
Inactive
 
Posts: 1588
Joined: 01 Sep 2006, 18:17

Re: 3.1 Beta reminder

Postby NoQ » 08 Mar 2012, 14:43

Cool (:

By the way, always been curious: who is allowed to join -dev? Cause it always says
#warzone2100-dev Cannot join channel (+b) - you are banned
to me :oops:
User avatar
NoQ
Elite
Elite
 
Posts: 5613
Joined: 24 Dec 2009, 10:35
Location: /var/zone

Re: 3.1 Beta reminder

Postby Emdek » 08 Mar 2012, 14:44

NoQ, that was discussed recently in another topic, let me find it...

Oops, I can't find it, was it removed?

AFAIR you need to have registered nick and don't log to IRC using web gate.
Nadszedł już czas, najwyższy czas, nienawiść zniszczyć w sobie.
The time has come, the high time, to destroy hatred in oneself.


Beware! Mad Qt Evangelist.
User avatar
Emdek
Regular
Regular
 
Posts: 1328
Joined: 24 Jan 2010, 12:14
Location: Poland

Re: 3.1 Beta reminder

Postby NoQ » 08 Mar 2012, 14:54

don't log to IRC using web gate.
Ok thanks this makes sense :oops:
User avatar
NoQ
Elite
Elite
 
Posts: 5613
Joined: 24 Dec 2009, 10:35
Location: /var/zone

Re: 3.1 Beta reminder

Postby JDW » 08 Mar 2012, 15:02

I have to say, 3.1 version is beginning to look like a serious kick-ass version. Whenever I host a game in 2.3.9 it always gets disconnected from the lobby plenty of times, but with 3.1, I seem to get a very reliable connection with the lobby and only rarely does it ever disconnect.
"Speak when you are angry and you will make the best speech you will ever regret."
-- Ambrose Bierce
User avatar
JDW
Regular
Regular
 
Posts: 1669
Joined: 18 May 2010, 19:44


Return to News and announcements