Why not instead of putting through all fixes and changes as they come, throw out an update every week? Seemingly daily as I come to the site something has changed, which is great -- it shows progress. However, with the rarity of release notes to this point, it's impossible to know what has changed. I understand minor bug fixes, timeout errors, and the like being implemented right away without a note, but what about major bug fixes (things that multiple people report consistently, or have a major impact on a section of the site/application)?
When I first signed up, and when phase 2/3 were released I thoroughly looked those things over. After seeing the extent of their "completion" at that time, I figured I'd check back and look for notes when things were updated, however that doesn't really happen (I think there have been 2, maybe 3 "release notes" since March). As such, as things are updated/changed I don't know about it unless I stumble upon it, subconsciously assume that features I previously looked at haven't changed, and may miss out on things that are updated for quite some time.
I would think on the back-end you would have an internal notes on who is working on what/fixing what bugs, etc. I'd imagine you have a "test" environment as opposed to this "production" available to us where you implement the fix and migrate over (but understand that might not be the case). The workflow would be, identify the fix/issue/update, implement it, note what was done, migrate to production. Once migrated to production (like I said, maybe once a week), release a "patch notes" that includes most of the things that were implemented and noted on the back-end, like
Fixed a bug where the long rest button wasn't working properly
Fixed a bug where page x wasn't displaying correctly in mobile
Released a large update to the non-mobile user interface, a summary of which can be found here
Added in additional filters to equipment
Resolved several minor bugs that were resulting in page timeouts and incorrect forbidden errors
If you did this weekly, the notes wouldn't be super daunting and go on forever (resulting in people actually reading them as opposed to seeing a giant post, reading the first few paragraphs and stopping). Separate the notes into sections like "New Features"; "Resolved Bugs"; "Updated interface design"; "Known issues". We would also have visibility on what changed on a regular basis, as opposed to finding out for ourselves "Oh they did fix the issue where the "Any Evil" filter wasn't actually finding all monsters with the "Evil" alignment" and having no idea how long that function was working and just dealing with the perceived inability to use it. Also, if you did this, create a new thread for each notes release rather than updating the same one (it's impossible to follow comments if you continue to update the same post over and over, as you cannot know what comments were made in relevance to each update).
Actually, even if updates were put in as they came up (as it appears to be done currently) instead of a weekly "patch" but weekly if you gave us a summary/release notes of what was fixed/changed/updated/released the last week I think it would be a great improvement.
Release/patch notes help -- they help us test the things you have changed with your updates to make sure the changes work well. I'd imagine you have to already have this internally, why not release them publicly
Actually, even if updates were put in as they came up (as it appears to be done currently) instead of a weekly "patch" but weekly if you gave us a summary/release notes of what was fixed/changed/updated/released the last week I think it would be a great improvement.
Release/patch notes help -- they help us test the things you have changed with your updates to make sure the changes work well. I'd imagine you have to already have this internally, why not release them publicly
This is exactly what is happening, starting two weeks ago with the release of the last two phases.
Expect another deployment today and a coinciding summary of release notes.
Actually, even if updates were put in as they came up (as it appears to be done currently) instead of a weekly "patch" but weekly if you gave us a summary/release notes of what was fixed/changed/updated/released the last week I think it would be a great improvement.
Release/patch notes help -- they help us test the things you have changed with your updates to make sure the changes work well. I'd imagine you have to already have this internally, why not release them publicly
This is exactly what is happening, starting two weeks ago with the release of the last two phases.
Expect another deployment today and a coinciding summary of release notes.
Thanks!
Awesome, thanks!
Rollback Post to RevisionRollBack
How do you get a one-armed goblin out of a tree?
Wave!
To post a comment, please login or register a new account.
Why not instead of putting through all fixes and changes as they come, throw out an update every week? Seemingly daily as I come to the site something has changed, which is great -- it shows progress. However, with the rarity of release notes to this point, it's impossible to know what has changed. I understand minor bug fixes, timeout errors, and the like being implemented right away without a note, but what about major bug fixes (things that multiple people report consistently, or have a major impact on a section of the site/application)?
When I first signed up, and when phase 2/3 were released I thoroughly looked those things over. After seeing the extent of their "completion" at that time, I figured I'd check back and look for notes when things were updated, however that doesn't really happen (I think there have been 2, maybe 3 "release notes" since March). As such, as things are updated/changed I don't know about it unless I stumble upon it, subconsciously assume that features I previously looked at haven't changed, and may miss out on things that are updated for quite some time.
I would think on the back-end you would have an internal notes on who is working on what/fixing what bugs, etc. I'd imagine you have a "test" environment as opposed to this "production" available to us where you implement the fix and migrate over (but understand that might not be the case). The workflow would be, identify the fix/issue/update, implement it, note what was done, migrate to production. Once migrated to production (like I said, maybe once a week), release a "patch notes" that includes most of the things that were implemented and noted on the back-end, like
If you did this weekly, the notes wouldn't be super daunting and go on forever (resulting in people actually reading them as opposed to seeing a giant post, reading the first few paragraphs and stopping). Separate the notes into sections like "New Features"; "Resolved Bugs"; "Updated interface design"; "Known issues". We would also have visibility on what changed on a regular basis, as opposed to finding out for ourselves "Oh they did fix the issue where the "Any Evil" filter wasn't actually finding all monsters with the "Evil" alignment" and having no idea how long that function was working and just dealing with the perceived inability to use it. Also, if you did this, create a new thread for each notes release rather than updating the same one (it's impossible to follow comments if you continue to update the same post over and over, as you cannot know what comments were made in relevance to each update).
How do you get a one-armed goblin out of a tree?
Wave!
Actually, even if updates were put in as they came up (as it appears to be done currently) instead of a weekly "patch" but weekly if you gave us a summary/release notes of what was fixed/changed/updated/released the last week I think it would be a great improvement.
Release/patch notes help -- they help us test the things you have changed with your updates to make sure the changes work well. I'd imagine you have to already have this internally, why not release them publicly
How do you get a one-armed goblin out of a tree?
Wave!
How do you get a one-armed goblin out of a tree?
Wave!