-
Notifications
You must be signed in to change notification settings - Fork 34
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
Establish versioning and release v0.1.0 now #2
Comments
Yes totally agree, good point and yeah please feel free to proceed. |
Actually should probably keep this open until done. :-) |
LOL. Yeah, I was beginning to wonder about that. It's all good. ;-) |
@afawcett - Please assign this one to me (this ticket exists on your project and I do not have "assignment privs"). Would you also create three milestones please? They should be something along the line of:
With those three we can set ticket #2 to the first milestone and then close it out and all future tickets can go to "0.2.0" or "Backlog" (or another milestone that we create in the future). Cheers! |
Ok done, I've added you as a Collaborator, not sure if that gives you any extra stuff. I'm fairly new to GitHub, so following your lead on this, much appreciated! :) |
Yeah. I saw the Collaborator notification just a moment ago. Thanks for that. I can assign tickets and create new milestones as well. I will test out "commit access" soon and will let you know. As to the question of "newness on GitHub," I hear ya. I am learning new things about GitHub all the time. What we don't know, we will figure out. I will get this ticket done soon (~ next 24-48 hours). Gotta finish up some work first before I can "play". ;-) Cheers! |
Ok. version 0.1.0 has been tagged via "maven release". The tag name is "sfdc-canvas-sdk-0.1.0" The pom version has been set to 0.2.0-SNAPSHOT. |
It occurs to me that we already have a release of this app on Heroku that folks are currently using. Since we are using Apache Maven, it would be good to codify that version now before we move forward. The version could be set to "0.1.0".
This way we can start working on version 0.2.0-SNAPSHOT and setup milestones around this (and future) version and we will not run into version confusion.
I can take care of the release now if needed, but I wanted to get your take, @afawcett before proceeding. Just let me know.
Cheers!
The text was updated successfully, but these errors were encountered: