-
Notifications
You must be signed in to change notification settings - Fork 90
Release 0.2 in May #60
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
Comments
If @pascalleclercq have time to do that, we could do that. But to be honnest with you, there is not a lot of new features for AngularJS. New features are about tern.java. So I'm not sure that it's very interesting for AngularJS. |
I believe the biggest gain would be feedback from users and #32 regular releases One more option is to have continuous release like in https://github.com/culmat/eExplorer |
you mean SNAPSHOT version? If it that it works liek this. Please read https://github.com/angelozerr/angularjs-eclipse/wiki/Installation---Update-Site |
That is nice. Then if @Nodeclipse picks up a version from SNAPSHOTs than it is like release, because we can reference (not only by date, but also by repository URL) |
Ok, I understand. @pascalleclercq will try to create a release this week if he find time. |
If you think that the current version is always ready for release. So there is such trick to do release. However I don't know what drawback could be for such way. |
Release is done for :
Many thank's @pascalleclercq ! |
Hooray! |
Updated wiki with (Or ref #36 |
@angelozerr Please update http://marketplace.eclipse.org/content/angularjs-eclipse BTW, You can ask Marketplace-service@ to add co-maintainers for the entry |
I have updated to 0.2.0 version. Is it OK?
Sorry, I don't understand what you mean. |
You can ask Marketplace admin to configure co-maintainers for some entries. Maybe for next time. |
Is it possible to release 0.2 of angularjs-eclipse (and tern.java) in May?
Nodeclipse train could pick-up them for its monthly release http://www.nodeclipse.org/history
The text was updated successfully, but these errors were encountered: