D 2.062 release

[Leandro Lucarella]

Steven Schveighoffer, el 18 de February a las 00:37 me escribiste:
> I propose that when you post the beta on the mailing list, you also
> post the reports of the fixed bugs and enhancements.  Then people
> can edit the descriptions before the release.  Then I think after
> the release, the descriptions should be locked, and the bugs cannot
> be reopened.

Please, don't do that, is the changelog what's broken, don't break the
issue tracker too to try to make a changelog out of it!

> I also would love to see an automatically generated changelog
> similar to the original based on the bugzilla data.  Can we add a
> "changelog description" field to bug reports so if the bug
> description (which arguably shouldn't be changed) isn't a very good
> changelog entry, that is used instead?

All we need to do is force people to update the changelog when making
a pull request. That's it. You are making everything more complex than
it should be...

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
Decile que ponga "rails generate tp_prof_fiuba" en la consola y en una
semana se recibe.
	-- Mazzi, filósofo estilista