[reSIProcate] releasing 1.9.0? changelog?

[Scott Godin]

My 2 cents on the change log.  Many people currently using the stack may
have no interest in the new features however would consider upgrading for
bug fixes.  Having to dig through 100's of commit logs is pretty
cumbersome.  Many commits are fixes for new features and not existing
(previous release) features and it is difficult for others to determine
which ones are which.
I'm willing to help generate the change log if others feel it is worthwhile
as well.

Scott


On Wed, Feb 5, 2014 at 8:58 AM, Daniel Pocock <daniel at pocock.com.au> wrote:

>
> How do people feel about releasing 1.9.0?
>
> There have been no complaints about the rc2 tarball so far
>
> The only thing potentially outstanding is the changelog, this can be
> created in the branch
>
> What level of detail do people really need in the changelog?  Now we
> have a Git mirror, anybody can clone the full repository to their local
> disk and conveniently browse  the full change history using gitk on
> Linux or Git Extensions for Windows.
>
> On that basis, I feel we could just include in the tarball
>
> a) a brief list of highlights
>
> b) an automatically generated summary of the commits since the 1.8
> branch was created
>
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20140205/37d98039/attachment.htm>