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.

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

Close and tag milestone v0.3 #15

Open
kengu opened this issue Nov 15, 2012 · 4 comments
Open

Close and tag milestone v0.3 #15

kengu opened this issue Nov 15, 2012 · 4 comments
Assignees
Milestone

Comments

@kengu
Copy link
Owner

kengu commented Nov 15, 2012

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.

@ghost ghost assigned kengu Nov 15, 2012
@igieon
Copy link
Contributor

igieon commented Nov 16, 2012

I have nothing. Only before release change libs from -src to compressed.

@kengu
Copy link
Owner Author

kengu commented Nov 16, 2012

@igieon - will do!

@leiva
Copy link
Contributor

leiva commented Nov 16, 2012

That 's fine for me .
Le 16 nov. 2012 18:50, "Kenneth Gulbrandsøy" [email protected] a
écrit :

@igieon https://github.com/igieon - will do!


Reply to this email directly or view it on GitHubhttps://github.com//issues/15#issuecomment-10455531.

@kengu
Copy link
Owner Author

kengu commented Nov 16, 2012

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants