Automatically generating CHANGELOG.txt from Github commits

[Mikko Ohtamaa]

Hi,

Do you know any method of automatically

* Extracting Git(hub) history

* Making CHANGELOG.txt entry like 1.0.2 -> 1.0.3

* Including text from history entries which are tagged like [release notes] and putting them to the changelog

This would make Python egg release process even better and more automatic with jarn.mkrelease and buddies.

[David Glick (GW)]

On Apr 11, 2012, at 12:09 PM, Mikko Ohtamaa wrote:

> Hi,
>
> Do you know any method of automatically
>
> * Extracting Git(hub) history
>
> * Making CHANGELOG.txt entry like 1.0.2 -> 1.0.3
>
> * Including text from history entries which are tagged like [release
> notes] and putting them to the changelog
>
> This would make Python egg release process even better and more automatic
> with jarn.mkrelease and buddies.
>

Only if everyone remembers to add the [release notes] tag when committing. Good luck with that.



----------
David Glick
 Web Developer
 [hidden email]
 206.286.1235x32

GiveBIG is coming! Mark your calendar for May 2 and get ready to give big to Groundwire
on this community-wide day of giving.

http://www.seattlefoundation.org/npos/Pages/Groundwire.aspx


_______________________________________________
Product-Developers mailing list
[hidden email]
https://lists.plone.org/mailman/listinfo/plone-product-developers

[Mikko Ohtamaa]

Hi,

>Only if everyone remembers to add the [release notes] tag when committing. Good luck with that.

I found myself more often forgetting to update CHANGELOG.txt by hand than entering commit notes... of course you cannot enforce such policy, but it would optimize workflow of people who actually use it.

-Mikko
 

----------
David Glick
 Web Developer
 [hidden email]
 <a href="tel:[phone]x32" value="[phone]">206.286.1235x32

GiveBIG is coming! Mark your calendar for May 2 and get ready to give big to Groundwire
on this community-wide day of giving.

http://www.seattlefoundation.org/npos/Pages/Groundwire.aspx

--
Mikko Ohtamaa
http://opensourcehacker.com
http://twitter.com/moo9000

_______________________________________________
Product-Developers mailing list
[hidden email]
https://lists.plone.org/mailman/listinfo/plone-product-developers

[ajung]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

A changelog should contain the _manually_ edited summary of changes
but not the single changes themselves. On particular change is perhaps
scattered over several commits. The change log must contain
human-readable information what has changed from the "big picture"
prospective
and not which ZCML files the developer has touched...
A change log is both for developers *and* integretors and dumb n00bs
but the commit history is for developers only.

- -aj

Mikko Ohtamaa wrote:

> Hi,
>
> Do you know any method of automatically
>
> * Extracting Git(hub) history
>
> * Making CHANGELOG.txt entry like 1.0.2 -> 1.0.3
>
> * Including text from history entries which are tagged like [release
> notes] and putting them to the changelog
>
> This would make Python egg release process even better and more
> automatic with jarn.mkrelease and buddies.
>
> -----
>
> Follow me in Twitter
>
>
>
> Read my blog
>
>
>
>
>
> -- View this message in context:
> http://plone.293351.n2.nabble.com/Automatically-generating-CHANGELOG-txt-from-Github-commits-tp7457162p7457162.html
>
>

Sent from the Product Developers mailing list archive at Nabble.com.
> _______________________________________________ Product-Developers
> mailing list [hidden email]
> https://lists.plone.org/mailman/listinfo/plone-product-developers

- --
ZOPYX Limited           | zopyx group
Charlottenstr. 37/1     | The full-service network for Zope & Plone
D-72070 Tübingen        | Produce & Publish
www.zopyx.com           | www.produce-and-publish.com
- ------------------------------------------------------------------------
E-Publishing, Python, Zope & Plone development, Consulting


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQGUBAEBAgAGBQJPhl36AAoJEADcfz7u4AZjedwLwLWjNDb0Etpll8t47Cg2lWZz
FC3mLCZAij9BEkkdGOr2QaSybbmT4pvneMJu0JCI4Nzy3aHr0xVuGG54CQ6HzUuc
EGfwVvVV7nMnhMkEdI3Hs8yWjYCIK0LSXOk5ZsKPNcELvYyeq5/H6rXX9trTmxf0
w4dRvcbSUeA4Ww01QFWkxkNk4Bx0WTAGGoBctQBZ6aDsGdjGN5KAGHeqBacF5dXD
pWZrxCpuhbtlm6xwLi4BHeJ8b8+m6JL+0CRxKiFvub6nZtCnE7ecpRbHDo1lOJTp
i+C/dK83jz7tYmtym/DseTcasHGihtMZGctHXxSXUAx4NuwxdJNfxpVLEYJTuug2
MbEAMKhpJ40y0Zmd1HpW6EN95iDbjIShGeJk5N47curk9dtad9V0SWgIU+NqAbd3
UE+IVmlvOMbuoevOeQEYdA9ErgAedRUxZOgI+KZqAALWlmGyncbLBTp0yDKCeG+q
6Cwk1wsCihgQo932C6ZhMUAZY9Sih0M=
=UVAq
-----END PGP SIGNATURE-----

_______________________________________________
Product-Developers mailing list
[hidden email]
https://lists.plone.org/mailman/listinfo/plone-product-developers