Nightly builds?

[Ter.Yeah]

Hi.

I understand the team is hard at work now, and I'm glad you're focused the way you are. I am sure I am not alone if I say that if 2.2 had been shipped with an "early access" / "beta" flag, tensions wouldn't be as high as they've been lately. With that in mind, would it be an idea to ship nightly builds to the beta branch? As the community has proven (for better or for worse, hehe), it's pretty adept at confirming/refuting fixes quickly.

I'm pretty sure we all want the same thing now, to get bugs ironed out, and as quickly as possible, and perhaps this is an idea that could help with the speed of that?

 

[Mímisbrunnr]

While not specifying a specific frequency, I'll agree with the generalized sentiment that it would be wonderful to get whatever is fixed sooner rather than later so that those playing in the meantime can avail themselves of the new improvements/fixes now and in the intervening interval till subsequent fix updates, rather than waiting for all to be distributed at once, leaving the game in its current state in the meantime.

You don't have to do it that way, but could you please consider it? I would view it as a win-win - players get some fixes that are ready now rather than waiting, and the devs can have the players confirm on a wider scale that the fixes are indeed working as intended.

 

[sillyrobot]

While not specifying a specific frequency, I'll agree with the generalized sentiment that it would be wonderful to get whatever is fixed sooner rather than later so that those playing in the meantime can avail themselves of the new improvements/fixes now and in the intervening interval till subsequent fix updates, rather than waiting for all to be distributed at once, leaving the game in its current state in the meantime.

You don't have to do it that way, but could you please consider it? I would view it as a win-win - players get some fixes that are ready now rather than waiting, and the devs can have the players confirm on a wider scale that the fixes are indeed working as intended.

It would also provide a mechanism for feedback when the fixes don't work or break something new.

OTOH, they would be a great pain for the dev team. If the nightly build is going to outsiders, then it must work -- no stubbing something for successful compilation because the work day is ending and the freaking code isn't doing what you told it to do. If others are going to use it then you need to document what the changes are so they might pay attention to that area and/or not freak out when weird crap happens because the stuff you're working on is about a 5-day fix and you're on day 2.

 

[Ter.Yeah]

It would also provide a mechanism for feedback when the fixes don't work or break something new.

OTOH, they would be a great pain for the dev team. If the nightly build is going to outsiders, then it must work -- no stubbing something for successful compilation because the work day is ending and the freaking code isn't doing what you told it to do. If others are going to use it then you need to document what the changes are so they might pay attention to that area and/or not freak out when weird crap happens because the stuff you're working on is about a 5-day fix and you're on day 2.

I'm pretty sure commits aren't pushed directly into the branch that goes into the CD pipeline. And if so, that would be a hassle for the internal testers as well

 

[sillyrobot]

I'm pretty sure commits aren't pushed directly into the branch that goes into the CD pipeline. And if so, that would be a hassle for the internal testers as well

Unless you are going to have the few devs push daily, there wouldn't be consistent nightly changes. And this change effectively expands the internal team to include the beta testers -- with all the issues that implies.