Schedule for any/next bug fix installment?

Azerack
Azerack Posts: 501 Critical Contributor
in MtGPQ General Discussion
I watch this list...

https://forums.d3go.com/discussion/61987/bug-status-list-updated-09-11-18#latest

....grow larger and larger from the onset of this last expansion and every time I think "Maybe they snuck in a fix to Blessing of Belzenlok" (or any other), I always am met with disappointment.

So, sorry if I'm the upteenth person to ask but when are ANY of these going to be fixed and see the light of day in-game?

Just curious... I know a lot off strategies are out the window until these get attended to...
Tagged:

Comments

  • Azerack
    Azerack Posts: 501 Critical Contributor
    @Brigby - Just calling out, here, since my post has had a few views but no responses (assuming no player would actually know but would want to...).. Can we at least know if 2.9 is going to contain fixes? Is there any chance of a more regular schedule for them?
  • Mburn7
    Mburn7 Posts: 3,427 Chairperson of the Boards
    Azerack said:
    @Brigby - Just calling out, here, since my post has had a few views but no responses (assuming no player would actually know but would want to...).. Can we at least know if 2.9 is going to contain fixes? Is there any chance of a more regular schedule for them?
    2.9 is going to have a lot of bug fixes (go and look at the bugs forum, you'll see a lot tagged as "fixed in 2.9")

    I would like to know when exactly it'll happen, though
  • GrizzoMtGPQ
    GrizzoMtGPQ Posts: 776 Critical Contributor
    I’m betting 9/20.
  • Azerack
    Azerack Posts: 501 Critical Contributor
    Mburn7 said:
    Azerack said:
    @Brigby - Just calling out, here, since my post has had a few views but no responses (assuming no player would actually know but would want to...).. Can we at least know if 2.9 is going to contain fixes? Is there any chance of a more regular schedule for them?
    2.9 is going to have a lot of bug fixes (go and look at the bugs forum, you'll see a lot tagged as "fixed in 2.9")

    I would like to know when exactly it'll happen, though
    I have, actually... But just waiting for 2.9 is like, "Well.... We're waiting!..." (annnd if you ever saw Caddyshack, you know the reference...).

    I was sort of hoping that they might institute a more formal bug fix schedule instead of the, "Well, lessee... maybe now? Whaddya think, guys?"
  • Brigby
    Brigby ADMINISTRATORS Posts: 7,757 Site Admin
    @azerack Well it also depends on the type of bug being fixed. Some things can be adjusted rather quickly, while other things require an entire new build. Due to this, we've historically bundled bug fixes into build updates, since most of them require a new build.
  • Kinesia
    Kinesia Posts: 1,621 Chairperson of the Boards
    Brigby said:
    @azerack Well it also depends on the type of bug being fixed. Some things can be adjusted rather quickly, while other things require an entire new build. Due to this, we've historically bundled bug fixes into build updates, since most of them require a new build.

    And you couldn't do something like "We'll release a new build with bug fixes every week!" because of the variability in time and testing and the apple approval process too, and the potential for bugs coming from the new release itself... Builds require more testing than the individual bug fixes, so the fewer bugs you have in a fix the more administration and wasted time you are adding to things...

    (But I'd approve of a build about a month after each set with all the  bugs that were able to be _Quickly_ solved by then!)
  • Azerack
    Azerack Posts: 501 Critical Contributor
    @Brigby - Thanks for the insight. I appreciate you responding to my question.

    However, I'm pretty sure any "build" is when you put a bunch of code together and call it such, right? So 2.8.0004 is still as much a "build" as 2.9... Or maybe the dev team have formal and informal "builds" or perhaps everyone works on a bunch of bugs on their own and nobody has to merge to "master" until everyone is done everything?

    To @Kinesia's point, I agree that mobile deployments are a little more of a hassle because you don't control the environment and they (Google and Apple, for instance) say what goes, but.. Still... Just thinking the bigger the builds you have, the more likely you are to have even more issues to go along with your fixes and less likelihood of saying, "Ah, that issue is probably because of this update." Also, considering I don't know how much testing your team (of QA? of Developers? both?) has before the scheduled deployment to "Production" every build has had some rather interesting problems that regression testing might have caught if they had time for it. - yes, probably conjecture and my apologies if this is so - 

    But also to Kinesia's thinking, a new build with "low hanging fruit" wouldn't be bad in a relative time after a major deployment, either. It would also allow a bigger build more time to get put together and tested.

    TL;DR - Just thinking that a minor bug fix build, occasionally, might help both players and the dev team avoid a larger number of issues during "expansion" or new event releases.

    Oh and kudos to the team for having a beta for the Duel Deck event! Even if I don't get picked for it, I hope they get a lot of good feedback from it.  :)








Categories