You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm just about ready to make the first official release. Snapshots are now deployed to Sonatype snapshot repository on every push to origin (working on limiting deployment to origin/master only, but Travis contains a bug preventing this). Next step is to stage and promote Maven artifacts for release.
Do you (@leiva and @igieon) have any thing in the pipeline that you want to include in this release?
I plan to complete milestone v0.3 within a week or so.
The text was updated successfully, but these errors were encountered:
Before the release, I will close all issues. This includes moving ownership to DISCOTools. This should not present any problem for maven users, since both stable and snapshot artifacts are available. All other users can download jars from the download section. I believe forked clones on github are updated automatically, but local clones must update the url to upstream/* repos. I will add user and developer documentation for all these cases before the release is completed.
After the release is deployed to Maven Central, I will announce the it on my blog, twitter and Leaflet community. Any other channels worth consideration?
Hi
I'm just about ready to make the first official release. Snapshots are now deployed to Sonatype snapshot repository on every push to origin (working on limiting deployment to origin/master only, but Travis contains a bug preventing this). Next step is to stage and promote Maven artifacts for release.
Do you (@leiva and @igieon) have any thing in the pipeline that you want to include in this release?
I plan to complete milestone v0.3 within a week or so.
The text was updated successfully, but these errors were encountered: