tag:blogger.com,1999:blog-17823979.post2524491422684809278..comments2023-09-29T05:03:51.672-04:00Comments on DivByZero.com: New & Noteworthy: Marketing Your Hard Worknickbhttp://www.blogger.com/profile/09200865148587349560noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-17823979.post-9419917357161822512008-11-14T18:43:00.000-05:002008-11-14T18:43:00.000-05:00Yeah, that's why I voted 2+3+4 on the poll. Great ...Yeah, that's why I voted 2+3+4 on the <A HREF="http://www.doodle.com/participation.html?pollId=64gndycncpksufx9" REL="nofollow">poll</A>. Great things to have, and everyone should have them... but I'm not sure they should be MANDATED.<BR/><BR/>That said, a list of fixed bugs is like a changelog. Great if you're looking for 'did bug X get fixed, and when?' or 'when did that regression happen?' but craptacular for marketing new features in a release to newbie users.<BR/><BR/>(Of course if the new release is just bug fixes, not new or noteworthy features, then, well, maybe it's sufficient.)nickbhttps://www.blogger.com/profile/09200865148587349560noreply@blogger.comtag:blogger.com,1999:blog-17823979.post-87336554888129969782008-11-14T18:15:00.000-05:002008-11-14T18:15:00.000-05:00There's value in good Javadoc, good wikis, a good ...There's value in good Javadoc, good wikis, a good home page, a good download page, good tutorials, a project file set, and so on. But none of those are required to meet a high standard. Why not? Surely no one would claim those aren't good things, so let's require them all! There's also value in fixing bugs, addressing features, blogging, answering newsgroups, and so on. Let's require all those too. I can think of lots of great things we could require, so let's keep that bar rising!<BR/><BR/>Then again, maybe accurate release notes with a list of bugzillas that have been addressed is sufficient for tracking progress and doing an excellent marketing job shouldn't be a make or break requirement.Ed Merkshttps://www.blogger.com/profile/05000982591510437551noreply@blogger.com