Proposal: Start requiring "code release notes" on a bug-level

[Jouni Heikniemi]

Christian Robottom Reis wrote:

> I'm thinking if updating the Developer Guide isn't what's missing --
> what do you think?

I think updating the Dev guide is parallel to this. We _need_ to have 
that updated as well, but which of you guys ever even take a quick 
glance at it? My point is, DevGuide is (should be) a reference and a 
tutorial, but it's not a newsfeed that lets you keep your 
Bugzilla-specific coding knowledge up-to-date.

If information about essential codebase updates were sent to this list, 
the person in charge of updating the devguide could fairly easily spot 
bigger issues just by reading developers at . This way, the regular 
developer information posted would also benefit the process of keeping 
devguide up to date.

It was a bad idea to even start using the term "release notes" in this 
discussion. I didn't come up with anything better and I still don't have 
a good idea, but it is confusing. Gerv is right: user-wise relnotes 
should be different and apart from this. If we don't group this "code 
knowledge" by release (which is fine, if we integrate it into devguide 
anyway), we don't have to find a way to automatically collect the 
information either.


Jouni