chancelog

[pushedx]

Any word on getting specifics in the change log? Obviously, you're no longer rewriting the entire bot every version, so you should be able to tell us what's going on. The problem with the way it is now is that I (and I imagine others) just find the first beta that works for me and halt updates on it until the next PoE patch, because I don't know of any fixes going in. What's the point in updating when I have a working version and have no idea what was added or fixed in the next one? There's always the chance you broke something that was already working fine, so the cost-to-benefit ratio is way off (cost = possibly broken bot version, benefit = unknown).

That would defeat the whole purpose of the beta.

Release is exactly what you are looking for in terms of finding something stable and sticking with it until the next PoE version.

Since we're coming off of a major rewrite, there was still/is some discrepancy between what Release should be vs how it actually was in terms of random bugs and stuff, but soon the Release version will begin to stabilize a lot more and be what it's supposed to be. We were doing a ton of updates every day and it made no sense to do them via beta and then rebuild release every 1/2 day, so we didn't. As a result, people took beta as being the latest and up to date bot, since that's what it was at the time.

Beta is really our development branch that is being tested publicly and built each 24 hours, regardless if we were finish what we were doing or not. This is something new being tried for Exilebuddy. People should expect it to break time to time, but it's necessary for us to be able to try out changes and rewrite things to have a better bot for the long term. Previously, we had to do a lot of work merging the changes from beta into release, but now, we are using a really simple system. If something was working fine, and then it breaks, we need people to be using it to tell us it broke, as chances are, those changes will eventually make their way into Release.

While not providing detailed change logs doesn't stop people from treating various Beta versions as Release, we aren't going out of our way to force people to use the latest beta by breaking the older beta versions. The trade-off is less in-depth notes, as sometimes we need to change things and see how users feel just by using it and not knowing exactly what changed. That way, we get unbiased feedback and no placebo effects of people pre-judging how the bot is based on what we say we changed vs how they see it run themselves.

So basically, there isn't that much more info to provide than the amount we update in the revision guide. If we were to post the SVN code commit logs, 99% of it is meaningless to users because you'd have to have access to the code to understand what was really changed. In addition, those logs are done in context of the code that was actually committed. We go through a lot of code that isn't even committed as we test things out.

Hopefully that makes sense.