Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Versioning #8

Closed
lichunqiang opened this issue Dec 25, 2015 · 3 comments
Closed

Versioning #8

lichunqiang opened this issue Dec 25, 2015 · 3 comments
Milestone
0.2.1

Comments

@lichunqiang
Copy link
Contributor

It should be followed the semantic versioning 2.0.0
@gaomd
Copy link
Member

gaomd commented Dec 25, 2015

There are two approaches I can think of:

  1. If the spec version is 0.3, then we name our package 0.3.0 ~ 0.3.9999, this way, we follow the spec and semantic versioning simultaneously, any better ideas?
  2. The thephpleague/commonmark project is doing another approach, which maintains an mapping table of package version to spec version.

Since in spec we defined interfaces specifically, I think it would be better for us to follow the 1st approach.

@lepture
Copy link
Member

lepture commented Dec 25, 2015

@gaomd the spec is a draft currently. It would be ok with any approach. When the spec goes to 1.0, we hope the versioning of implementations would be 1.x.x. The spec will be 1.0, 2.0, 3.0, spec itself will never be something like 1.1.

@gaomd gaomd modified the milestone: 0.2.1 Dec 31, 2015
@gaomd
Copy link
Member

gaomd commented Dec 5, 2016 •
edited
Loading

Discussion moved cn/GB2260#34

@gaomd gaomd closed this as completed Dec 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.2.1
Development

No branches or pull requests
3 participants
@gaomd @lepture @lichunqiang