the new & improved known issues wiki page! (in General)
after discussing with nightstrike ways to improve our bug reporting in cb, i have decided to revamp and simplify the known issues page of the wiki.
the new page is broken down into high and low priority as well as a section for issues awaiting prioritization. most of us will just be placing any new issue in the "issues awaiting prioritization" section until we hear where it fits best.
i also do not mind people chatmailing me links with bug threads and letting me post them. if you do post them yourself, please follow the suggestions at the top of the wiki known issues page.
all of the older bugs have been placed in low priority but i need to go through them with ns as some have been fixed.
there is more coming regarding this topic, but i have to go for now.
April 29 2010 3:07 PM EDT
everyone is welcome!
i added a new category entitled:
Very Low Priority or Too Much Time For Too Little Gain
i think it is self-explanatory. i have also moved some things to that section with nightstrike's input.
i added one more category and this should be the last one: Fixed, Can Be Removed Once Tested
April 30 2010 7:28 AM EDT
in the past i had often waited for player consensus on issues where i was unsure whether we were dealing with a bug or not. the vorpal blade bug brought up why this may not be the best policy and has made me decide to be more proactive in adding bugs to the known issues page, trying to solicit help from community members and then screening them for ns.
with that being said, if you see a bug thread with no post by me, or anyone else, stating that it has been added to known issues, please let me know or add it to the section waiting for prioritization and let me know so that maybe i can get some help investigating it.
This thread is closed to new posts.
However, you are welcome to reference it
from a new thread; link this with the html
<a href="/bboard/q-and-a-fetch-msg.tcl?msg_id=0032pF">the new & improved known issues wiki page! </a>