On Tue, Mar 18, 2014 at 12:00 PM, Jeremy Rossi <[email protected]> wrote: >>> # Use the Pull Requests Not the Commits #################### >>> >>> To create the release notes I would use the Pull Requests themselves. >>> They reflect a complete idea that is merged into master. Their are also >>> all kinds of tools to help out with this. I started writing one in >>> python but I will let someone else take over. Here is the code: >>> >>> https://gist.github.com/jrossi/a7934a436fef3811f97e >>> >>> This has two files the python code to make the markdown release notes >>> from github pull requests. It's far from complete but should make >>> release note generation easy. If we want to control what goes into the >>> release notes. Just use pull request tags or milestones or what ever. >>> >> >> I'll stop working on the release notes immediately. >> > > Hope it helps; doing things like this should be done by a computer they > are better at it and it frees you up to do the fun and hard stuff. >
Hope what helps? It's one more reason not to pay attention to the commits. > > -- > > --- You received this message because you are subscribed to the Google > Groups "ossec-list" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
