Loggregate v0.2.2

Release v0.2.2

Optimizations

• Refactored code and made a couple of optimizations #2 #3

To verify the signature on the release tarball...

First import my pgp public key

gpg --recv-key C8B2A95D8D855A9D8C6F0C78BCBCAE31ECE05007

Then verify the signature

gpg --verify loggregate-0.2.2.tar.gz.asc loggregate-0.2.2.tar.gz

Full Changelog: v0.2.1...v0.2.2

Loggregate v0.2.1

Release v0.2.1

Bugfixes

• Fixed bug related to --help #1

To verify the signature on the release tarball...

First import my pgp public key

gpg --recv-key C8B2A95D8D855A9D8C6F0C78BCBCAE31ECE05007

Then verify the signature

gpg --verify loggregate-0.2.1.tar.gz.asc loggregate-0.2.1.tar.gz

Full Changelog: v0.2.0...v0.2.1

Loggregate v0.2.0

Release v0.2.0

Breaking changes

• Users no longer need to pass datetime start and end positions or loglevel start positions, loggregate finds them using regex.

To verify the signature on the release tarball...

First import my pgp public key

gpg --recv-key C8B2A95D8D855A9D8C6F0C78BCBCAE31ECE05007

Then verify the signature

gpg --verify loggregate-0.2.0.tar.gz.asc loggregate-0.2.0.tar.gz

Full Changelog: v0.1.0...v0.2.0

Loggregate v0.1.0

First Release

To verify the signature on the release tarball...

First import my pgp public key

gpg --recv-key C8B2A95D8D855A9D8C6F0C78BCBCAE31ECE05007

Then verify the signature

gpg --verify loggregate-0.1.0.tar.gz.asc loggregate-0.1.0.tar.gz

Full Changelog: https://github.com/akashters/loggregate/commits/v0.1.0