delta/ruby-gems/hashie.git - github.com: intridea/hashie

	Commit message (Collapse)	Author	Age	Files	Lines
*	Update github urls to hashie/hashie (#497)	Bobby McDonald	2019-11-17	1	-4/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* Update github urls to hashie/hashie * Point omniauth in integration tests at master. Until omniauth releases the changes merged from https://github.com/omniauth/omniauth/pull/977 , we must point at master branch. * revert incorrect change of gem email Co-Authored-By: Michael Herold <github@michaeljherold.com> * Reference open issue for release
*	Prepare for next development iteration, 3.5.5	Michael Herold	2017-02-22	1	-2/+2
\|
*	Preparing for next development iteration, 3.4.6.	dblock	2016-09-16	1	-8/+8
\|
*	Preparing for the next development iteration, 3.4.5.	dblock	2016-04-29	1	-1/+3
\|
*	Update the change log format	Michael Herold	2016-02-01	1	-13/+54
\| \| \| \| \| \| \| \|	By updating to the "Keep a Changelog" format, we can more easily identify changes that necessitate different levels of version bump. This change updates the changelog to the new format and updates the contributing and releasing guides with new instructions based on the new changelog format.
*	Add releasing policy	Michael Herold	2014-08-25	1	-0/+83
	This is based on [Grape's release policy][grape], per discussion. I left out the section on making an announcement, since there isn't a news group for Hashie to the best of my knowledge. Does this process look complete? Is anything confusing or wrong? [grape]: https://github.com/intridea/grape/blob/master/RELEASING.md