The explanation is illogical at best and specious at worst. "Let's delay a patch to include a fix that isn't going to fix anything currently active in-game". The current CG will be over when the patch is released. Delay the next CG instead. ...if there's even one scheduled.
That wasn't the reason. Go read it again.
we'd like to implement an additional fix to a present, reported issue which causes unintentional Community Goal abandonment.
- A poignant example of this issue being that 'if you attempt to abandon any missions, it will abandon the CG you signed up for'.
Delay it for an additional fix, the most illogical thing. Instead of pushing one fix when it's ready we gona wait for more fixes..I'm sorry, but update 7? We are in mid sep, release of Odyssey was months ago. And what is FD doing? Only fixing broken stuff which should never been released in its state.
Where is the new stuff? New ships, new SRVs f.e?
No applause from me
Do you have any C\C++ programming experience? I know Frontier has positions open, get in there and show them how it is done.680 people emplyed by Frontier.. why do we get the feeling that there are only 2 that can code working on Elite??
It destroys any hope the game can be what we want it to be when bugs cause delay after delay after delay. We are a third of a year past release now. I feel sorry for whoever is left actually coding, they need help and a lot more of them. You have the numbers Frontier..what on earth is going on over there in Cambridge?
(edited because I was right the first time, a third of a year from release by all intents and purposes)
All you've done is quote the fix. Read why they are putting it in with update 7 (and delaying update 7) instead of having it as a separate patch. It's all in this thread. Just click on Dev post to get to the next Dev post in the thread and you will come across it.The explanation is illogical at best and specious at worst. "Let's delay a patch to include a fix that isn't going to fix anything currently active in-game". The current CG will be over when the patch is released. Delay the next CG instead. ...if there's even one scheduled.
Depends on the fix and if it's vital to have that fix in for a specific time. Waiting another month to add that fix in would be illogical then delaying the update to come out by a small amount of days.Delay it for an additional fix, the most illogical thing. Instead of pushing one fix when it's ready we gona wait for more fixes..
Given that you are having this under your belt, and given that the issue tracker still lists it as confirming.... would it be possible to change the process to mark items under your belt in the issues tracker somehow? Maybe to "acknowledged" or "confirmed", so that the reporter has feedback that someone is looking at this instead of letting it move into "expired" (as there are not enough players looking in the issue tracker in a way that sensible issues reach the "confirmed" state).Heya Floss! This has been under my belt for a time now so don't worry, eyes are on it.
What? Inefficient? CD/CI is inefficient now? Really?Depends on the fix and if it's vital to have that fix in for a specific time. Waiting another month to add that fix in would be illogical then delaying the update to come out by a small amount of days.
What you think they should do, is a very inefficient way to do stuff, which is precisely why they aren't doing it.
We already know the results of relatively fast updates, and we know they can't do it without breaking a lot of things every update, so it's better they properly cook the updates than getting them out too fast (in addition i belive they have a very complex structure and they can't deploy a single fix without moving a lot of parts).What? Inefficient? CD/CI is inefficient now? Really?
Btw separating 2 fixes is not inefficient Infact it's hight efficient. The faster you fix smth the less annoyed your customer is from this bug. Therefor your goal is to fix any bug asap. With weekly updates you would minimize the downtime while still maintaining high fix density and that is very preferable over 2 month of no patching and annoyed customers.
We really don't know their DevOps practices to comment whether CI/CD would be efficient for the ED codebase.What? Inefficient? CD/CI is inefficient now? Really?
Btw separating 2 fixes is not inefficient Infact it's hight efficient. The faster you fix smth the less annoyed your customer is from this bug. Therefor your goal is to fix any bug asap. With weekly updates you would minimize the downtime while still maintaining high fix density and that is very preferable over 2 month of no patching and annoyed customers.
They've never asked me how I amEverybody asking how much devs working on elite
But nobody asking how are devs((
Keep up the good work, team!
Was it Mike Evans who'd smash his fist through the screen at you in heated forum PvP?They've never asked me how I am![]()
When I first stopped by the Frontier forum, it was pretty dull as ED wasn't announced and the tumbleweed rolled from thread to threadWas it Mike Evans who'd smash his fist through the screen at you in heated forum PvP?
Early forum days were interesting![]()
Back when FD was not the corporate juggernaut it is now and ED was a scrappy contender the dev / audience interplay was great.When I first stopped by the Frontier forum, it was pretty dull as ED wasn't announced and the tumbleweed rolled from thread to thread![]()