tag a version

Open KJLJon opened this issue 8 years ago • 2 comments

I think a version should be tagged so it will be easier to install via composer. I recommend following symver

I am open to either one of these versions (depending on what your thoughts of the stability of the package is):

0.1.0 - if you think there still might be major changed / API changes
1.0.0 - if you are are pretty set on the packages public API.

Dec 12 '17 03:12 KJLJon

Argeed. If we can get the KDF stuff handled quickly (viz. #5 and #11) and bump CryptoKey to k1|..., I’d say version 1.0.0. I’d accept a PR for 0.1.0 at any time; I’m actually reasonably pleased with the API as it stands.

Dec 12 '17 06:12 starekrow

I am almost done with #5, and was going to try to work on #11 at the same time (in the PR) so the key only has to be bumped up to k1 instead of k1 and k2.

Dec 12 '17 12:12 KJLJon