search

wechaty / java-wechaty-getting-started

Java Wechaty Starter Project Template that Works Out-of-the-Box
https://gitpod.io/#https://github.com/wechaty/java-wechaty-getting-started
Apache License 2.0
47 stars 41 forks source link

THE semver for Java Wechaty #8

Closed huan closed 4 years ago

huan commented 4 years ago

Currently, our Wechaty project is using the semver, start from version 0.0.1.

The latest wechaty on npm is v0.39

So I'd like to suggest that our Java Wechaty follow the same versioning style, and start from version 0.1.0

Also, npm and pip all have a dev version so that we can publish a version for the beta users, and at the same time, the release user will not see the beta version.

To archive that, npm has the @next version instead of the latest, and the pip has a -dev for PRE-RELEASE.

It would be great if our Java Wechaty can use the same method to differentiate those two published versions, if the maven system has the same pattern for the publishing.

diaozxin007 commented 4 years ago

mvn has snapshot version.

huan commented 4 years ago

That's great!

Then we can follow the same semver versioning rule and the publish patterns from the Wechaty Org for our Java Wechaty:

  1. odd minor version number will be CI/CD to snapshot for beta users.
  2. even minor version number will be CI/CD to the production.