On Feb 18, 11:10 pm, Carl Meyer <carl.j.me...@gmail.com> wrote: > Hi Russell et al, > > I don't agree with the wontfix resolution of #15330. I think the OP > there is right - we should be consistent in providing release notes > for all releases, even if they would be as short as "No significant > changes" (and I don't actually think that's true even for 1.2.1 or > 1.2.3 -- in both cases the reason for the additional release on short > notice is in itself worthy of note in release notes). > > If release notes are simply missing, someone about to upgrade to that > release has no way to be sure if they're missing because they weren't > considered necessary, or if they're missing because of a mistake (such > mistakes have certainly been known to happen), or because they're > trying the wrong URL, or... Clarity is important, and the effort > involved here is minimal. If the effort involved concerns anyone, I'm > quite happy to be the volunteer to make sure release notes exist for > all releases.
Of course I agree with Carl :) I should enforce my point that at least a link to the blog should be there. Personally I tracked it down and it took me a couple of minutes, to figure out why they where missing. But the confusion was there as well as a potential problem with more picky organizations (like packagers or pointy hair bosses) > > Carl -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
