search

liteserver / binn

Binary Serialization
Apache License 2.0
441 stars 58 forks source link

Specification and version #20

Open ghost opened 6 years ago

ghost commented 6 years ago

Hi,

Currently specification doesn't include version and/or published date. May I ask if you could do so?

Just for example, one format CBOR has details about published date. It doesn't have version, but (I think) the document name RFC 7049 can be used like a version name.

In terms of using version, may I ask if you could consider adopting semantic versioning?

Thank you,

kroggen commented 6 years ago

Hi!

I saw that the spec.md file was created here on July, 9 2015. Although I worked on it for more than one year before that. We can consider this date as the release to public.

We could use semantic versioning, but which would be the current version?

It can be 1.0.0 and then we discard the bug fixes made until here. Or maybe we could count the bug fixes and use the right number in the patch section.

ghost commented 6 years ago

@kroggen

Thanks for your response.

I think using that file creation date as published date is ok. For version, the README file already stated that current version is 1.0. Maybe you can use that. Also as I'm new to the project, and since you have worked on the project for a very long time, I think it's better that you decide which version should be.

kroggen commented 4 years ago

Semantic versioning was adopted using tags.