[colecampbell666]

I've asked this several times in several threads with no response, so I figured that I should ask formally.


What is the current planned release date for 3.6.10?

[Kazan]

as soon as you shorten your signature

[Flipside]

'When it's ready' is the only answer that can be given, because it's the only answer there is.

It's important people understand that, if something comes up in one of the coders lives and they have to take a few weeks off, and the project gets held up, then that's the way things go. A bug might crop up at the last minute that leads back into a huge twisted section of code, that's just the way things go. The source code does not work to dates, it works to achievements, once they have reached a level where a release is warranted and the build appears to be stable, then they will release it.

[colecampbell666]

k.

[Flipside]

If it makes you feel better, you will get an announcement when it comes out, don't worry, you won't miss out on 3.7 when it comes out, and it will be worth the wait

[Topgun]

If it makes you feel better, you will get an announcement when it comes out, don't worry, you won't miss out on 3.7 when it comes out, and it will be worth the wait

he might miss out on 3.610 though .

[Flipside]

LOL To be honest, I was under the impression the next official release was 3.7, but I could be wrong, so I didn't say either way

[Hades]

If it makes you feel better, you will get an announcement when it comes out, don't worry, you won't miss out on 3.7 when it comes out, and it will be worth the wait

he might miss out on 3.610 though .

There will be a 3.610.0?

[colecampbell666]

If it makes you feel better, you will get an announcement when it comes out, don't worry, you won't miss out on 3.7 when it comes out, and it will be worth the wait

Poor 3.6.11, no attention whatsoever...

[Polpolion]

The only people who can have release dates are people who do this stuff as their job. They get fired if they stop working.

[haloboy100]

but nobody has a job in this, so therefore there is no official release date.

[Inquisitor]

Given the number of bugs in the current codebase, any official release may be a while unless we get some real bug hunting and killing done.

[YemminatoR]

i compiled the cvs versione of fs2open and i see in the hangar fs2 open 3.6.10

[Snail]

Maybe have a Code phase completely dedicated to finding, torturing and then killing bugs.

[ni1s]

i compiled the cvs versione of fs2open and i see in the hangar fs2 open 3.6.10

Yeah, what's up with that? Why is the fs2_open_3_6_9 branch still being commited to? Why isn't there a fs2_open_3_6_10 branch? It's a bit confusing... 

[karajorma]

Everyone just kept committing to the 3.6.9 branch after it was out.

[Inquisitor]

Maybe have a Code phase completely dedicated to finding, torturing and then killing bugs.

Those are the infamous code freezes. And its probably not a bad idea...

As for getting a clean copy of 3.6.9 you can still get by date, just find the release thread and get code from before that date (or within a couple days afterwards).

[castor]

Everyone just kept committing to the 3.6.9 branch after it was out.

[just wondering]
Is it gonna go the same way in future releases? At least for us users it would be clearer if a branch was dedicated for bug fixes only after the release.
[/just wondering]

[Inquisitor]

Ideally, no, it should not be that way.

Some of it depends on the stress levels and numbers of the volunteers.

[karajorma]

As a person who did an appreciable share of the support on this forum under the older system I'd prefer to keep it this way with a stable and development branch.

However we shouldn't be leaving two year gaps between official releases from HEAD after 3.7.