You're getting close to 5.0

[TechSY730]

This is here as a word of encouragement. You probably already know all this, but I want to let you know I can see how well you are doing too.

You are getting really close to 5.0 here

In fact, I did a search on Mantis, with these filters

Severity: trivial, text, tweak, minor, major, crash, block
Status: new, feedback, acknowledged, confirmed, assigned
Resolution: open, reopened

And only got 24 issues left. You're so close!

[Tridus]

Keep up the good work! Looking forward to a great release soon.

[x4000]

Yup, and most of those won't be pre-5.0.  A lot of them just haven't gotten bumped yet to the considering or whatever other status.

There's a quick way to see that list, which is the Developer To-Do List By Date in the filter dropdown in the middle of the screen, btw.

Thanks guys!

[keith.lamothe]

Thanks

Yea, at this point it's basically just

1. Wait until the desyncs stop happening long enough to be comfortable with (those things are like stalking AI threat).
2. Fix any crashes or other game-enjoyment-destroying stuff that crops up.
3. Finish up some documentation, etc.  Some tutorial updates (for the core shield network, at least).

[TechSY730]

...
1. Wait until the desyncs stop happening long enough to be comfortable with (those things are like stalking AI threat).
...

Well, I hope they don't start putting those waiting desyncs into carriers and rushing you guys with them. I don't even know what that would mean, but I know it wouldn't be good.  

[Mithror]

Oh, don't worry about that. They can always build some space docks and have them rally autobombs to the wormhole being stalked.

Of course... they could be immune to area damage... D:

[keith.lamothe]

Of course... they could be immune to area damage... D:

Actually that would be a very good analogy, most of our normal "carpet-bombing" approaches to reproducing, tracing, and fixing bugs simply don't work on desyncs

[TechSY730]

Of course... they could be immune to area damage... D:

Actually that would be a very good analogy, most of our normal "carpet-bombing" approaches to reproducing, tracing, and fixing bugs simply don't work on desyncs

I sure hope you didn't spend all your knowledge on flak and lightning debugging approaches.

[keith.lamothe]

I sure hope you didn't spend all your knowledge on flak and lightning debugging approaches.

I'd much rather use a Heavy Beam Cannon

[Echo35]

So is there a projected release date/time frame?

[keith.lamothe]

So is there a projected release date/time frame?

Whenever we're confident the desyncs have stopped, basically.

[BobTheJanitor]

I can't take it any more. Can someone correct the thread title? It should be You're, not your.

[TechSY730]

I can't take it any more. Can someone correct the thread title? It should be You're, not your.

Derp. My bad. Sorry about that. I can't believe I missed that.
Fixed.

[zebramatt]

I can't take it any more. Can someone correct the thread title? It should be You're, not your.

You caved! I've been resisting the urge to mention it for days!

[BobTheJanitor]

Derp. My bad. Sorry about that. I can't believe I missed that.
Fixed.

My hero!