Closed urandom2 closed 5 years ago
Thanks! I don't feel OK marking it 1.0 without some updates in the readme etc. (regarding e.g. the _amd64 naming, which is now a recommended practice and should be explained there), but then I can't get to maintaining/gardening this project properly anymore... I put it on https://www.codeshelter.co/ recently; not seeing much help from there yet, but it's a very fresh thing, so I assume we need to be patient to see if it gets enough traction and support...
makes total sense, and thanks a bunch for the merge; would you be willing to tag it as v0.1.0
, v0.9.0
, or v1.0.0-rc
, as none of these bind you to the compatibility guarantees of v1.0.0
?
Great idea, thanks! It appears I'm not educated in modules well enough yet, in my mind I somehow believed v0.x.y behaves similar to the v0.0.0-... pseudo-version. Cool, v0.8.0 marked, thanks again. :heavy_check_mark:
v1.0.0
v0.0.0-20170831122431-f6a15ece2cfd