Please release version 2.9

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run current release, 2.8
1a. After a variable amount of time, notice crash (as previously reported)
2. Or run special release mongoose.27Aug2010.exe.
2a. Note that program exits immediately.

What is the expected output? What do you see instead?

I expect mongoose.exe to run. I see either a crash or no running.

Please use labels and text to provide additional information.

I am using Mongoose actively to develop software. I must have a version that 
works immediately. Thank you.

Please consider creating a version tree, so multiple versions can be obtained 
and so that multiple subversions of versions can be developed. The current 
release should be only one of two or more that are available. That way some 
bugs can have the workaround of using a different version.

Original issue reported on code.google.com by googl...@springtimesoftware.com on 31 Aug 2010 at 6:41

• Merged into: #165

[GoogleCodeExporter]

Please make sure you don't have old mongoose.conf lingering in a directory.
2.9 and 2.8 have different options format.

Original comment by valenok on 31 Aug 2010 at 6:47

[GoogleCodeExporter]

Original comment by valenok on 31 Aug 2010 at 6:48

• Changed state: Duplicate

[GoogleCodeExporter]

I should have stated that this issue refers to Windows only, since I only use 
Windows XP Home SP3.

I have no old versions of mongoose.exe in use, only 2.8 and 
mongoose.27Aug2010.exe. I do not use them simultaneously. To the best of my 
knowledge, 2.9 does not and never has existed. I looked for it about five 
minutes ago and could not find it.

Original comment by googl...@springtimesoftware.com on 31 Aug 2010 at 6:52

• Added labels: OpSys-Windows, Usability

[GoogleCodeExporter]

Also, if the man page has changed, there needs to be two subtrees: one for the 
2.8 man and one for the 2.9 man.

You used to do versions correctly in Google Code. What happened?

Original comment by googl...@springtimesoftware.com on 31 Aug 2010 at 6:54

[GoogleCodeExporter]

1. Mongoose moved from SVN to Mercurial. SVN repository is accessible, and you 
can find all previous versions at http://mongoose.googlecode.com/svn/tags/
2. On Mercurial, not a single release has been cut yet, so there are no 
tags/versions. 2.9 will be the first one.
3. mongoose.27Aug2010.exe and mongoose.31Aug2010.exe are both pre-release of 
2.9 and could be downloaded  from 
http://silversoft.net/~devnull/tmp/mongoose.27Aug2010.exe and 
http://silversoft.net/~devnull/tmp/mongoose.31Aug2010.exe respectively
4. Both binaries work fine on my system, which is Windows XP sp3
5. I asked you to make sure there is no mongoose.conf used. Best way to test is 
to copy executable into some empty directory, run a console, "cd" to that 
directory and run "mongoose -e errror.log"

I'd be happy to help via IM (gtalk) to debug this problem faster.

Original comment by valenok on 31 Aug 2010 at 7:11

[GoogleCodeExporter]

1. Sorry, I have no idea what Mercurial is. Google Code seems to support only 
SVN?

2. I looked at http://mongoose.googlecode.com/svn/tags/ and found only up to 
2.8. There should be a 2.8.1 that fixes the crash bug.

3. In general, you should release crash fixes separately from new function 
releases. I'm sure you must already know this. Major versions should relate to 
functionality, especially if they are backward-incompatible. Minor versions are 
bug fixes only.

4. File http://silversoft.net/~devnull/tmp/mongoose.31Aug2010.exe does run when 
there is no config file, but seems to fail to close on Ctrl-C. On windows (and 
maybe on other OSs too?) a signal is not needed. Simply closing the window or 
terminating the process automatically closes all child threads. Waiting for 
child threads to close was only needed in the 1970s, if at all then. Correct me 
if I'm wrong.

5. I still find only 2.8 materials on the main mongoose page, 
http://code.google.com/p/mongoose/. If the almost-2.9 releases have different 
config requirements, I need a new man page (Manual) or a software tool to 
convert from the old config to the new config.

6. Thanks for offering to IM. Fortunately, I have another computer that runs 
Apache, so I'm only relying on mongoose on the other computer. This gives me a 
workaround. If we ever have a really important feature to discuss, IM might be 
very good for that.

Original comment by googl...@springtimesoftware.com on 1 Sep 2010 at 12:46