Engine Testing - 95.0.1-230-gfee8fe3 (31. Dec. 2013)

[abma]

release candidate #2 for 96.0!

only 19 commits since RC1:
https://github.com/spring/spring/compar ... 0-gfee8fe3

download

changelog.txt (is currently the same as for rc1)

no breaking changes known atm since 95.0

If you find a bugs, please report to Mantis.

Please attach infolog.txt as file, if you crash!

maybe as note: if no major bug is found i'll tag 96.0 on 25.12. and make it default version on lobby server one week later if no major/blocking bug is found.

[smoth]

Nope. Not ready. In fps camera, if you look down then move to the right or left, before it would rotate around. Now it is stuck in the down position and refuses to rotate.

[knorke]

http://springrts.com/mantis/view.php?id=4235
that is why it always says "If you find a bugs, please report to Mantis."

[smoth]

http://springrts.com/mantis/view.php?id=4235
that is why it always says "If you find a bugs, please report to Mantis."

my point is, he needs to go ahead and update to the version after they fix it. I get that you are trying to dictate to us all how you feel things should be done but it doesn't really matter, we need a new rc already.

[Kloot]

"you are trying to dictate to us"

"he needs to go ahead and update to the version after they fix it"

abma made the RC in good conscience before that issue (the importance of which is being vastly overstated like all minor crap around here these days) was even reported and you can shut the fuck up now.

[smoth]

abma made the RC in good conscience before that issue (the importance of which is being vastly overstated like all minor crap around here these days) was even reported and you can shut the fuck up now.

I think a new rc is in order before we have several other "fixes" get shoved in last minute. He wants to test a specific build before release, I am ASKING him to post the next build he wants as a RC so I can go "shut the fuck up" and test it. I love you to.

[Kloot]

"I am ASKING him to post the next build he wants as a RC"

There isn't going to be a new RC for every insignificant little bugfix that gets pushed in the interim and if you want to claim this particular issue *somehow* makes testing impossible you can download a more recent buildbot installer.

[knorke]

I get that you are trying to dictate to us all how you feel things should be done

It is not something I dicktate: using bugtrackers to report bugs is not really a new concept.

In the first post of this thread it clearly says If you find a bugs, please report to Mantis.
And yet you posted in forum.

Not the first time btw, you seem to do it all the time. For example here you were told that "bug was already reported":
http://springrts.com/phpbb/viewtopic.ph ... 20#p551003
Even with link to bug.
And then you still post again:
https://github.com/springlobby/springlobby/issues/140
http://springrts.com/phpbb/viewtopic.ph ... 20#p551809
Imo nobody can be so stubborn so it must be trolling.

[smoth]

He said that

rmaybe as note: if no major bug is found i'll tag 96.0 on 25.12. and make it default version on lobby server one week later if no major/blocking bug is found.

It might not be a major bug, but being that I use fps camera, it is a big deal to me. So I don't want to see this issue in the next release. So since this is fixed why not do another rc? If it is all gravy, why not?

[abma]

In the first post of this thread it clearly says If you find a bugs, please report to Mantis.
And yet you posted in forum.

this wasn't always so, in older testing "releases" it was written sth. like post here or to mantis, but as it didn't work well (bug reports were lost because of to many posts in the thread) only mantis should be used for bug reports.

so please all calm down, nobody was hurt (and use mantis to report bugs).

thanks!


also doing an rc about every tiny change makes few sense as every build would be then an rc and these are sometimes >10 a day.

i make an rc to make sure all builds are available. also i check validation test, test myself a bit if i find something major. it doesn't make sense to release sth. when for example no build is available or it doesn't compile or it doesn't start at all.

imo it works atm quiet well as bugs are reported and fixed. some are not in mantis but at least they mostly aren't reported twice.

[smoth]

So we are moving along well? I am not sure I can really help all that much testing later but I am trying! Do you want me to continue with this build or get the latest build bot under dev??

[abma]

if you can, please use newest available build in the release branch.

http://springrts.com/dl/buildbot/default/release/

else use the rc.

edit: oops, wrong topic was set. (but links, etc were fine)

[smoth]

excellent, do we have anything in particular that has been a major concern?

[abma]

atm nothing known... should be quiet stable / in releaseable state.

[abma]

first test release after 96.0 release:

http://springrts.com/phpbb/viewtopic.php?f=12&t=31733