{"action":"created","issue":{"url":"https://api.github.com/repos/eclipse/smarthome/issues/612","labels_url":"https://api.github.com/repos/eclipse/smarthome/issues/612/labels{/name}","comments_url":"https://api.github.com/repos/eclipse/smarthome/issues/612/comments","events_url":"https://api.github.com/repos/eclipse/smarthome/issues/612/events","html_url":"https://github.com/eclipse/smarthome/issues/612","id":120161999,"number":612,"title":"Version bumps / releases","user":{"login":"kaikreuzer","id":3244965,"avatar_url":"https://avatars.githubusercontent.com/u/3244965?v=3","gravatar_id":"","url":"https://api.github.com/users/kaikreuzer","html_url":"https://github.com/kaikreuzer","followers_url":"https://api.github.com/users/kaikreuzer/followers","following_url":"https://api.github.com/users/kaikreuzer/following{/other_user}","gists_url":"https://api.github.com/users/kaikreuzer/gists{/gist_id}","starred_url":"https://api.github.com/users/kaikreuzer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kaikreuzer/subscriptions","organizations_url":"https://api.github.com/users/kaikreuzer/orgs","repos_url":"https://api.github.com/users/kaikreuzer/repos","events_url":"https://api.github.com/users/kaikreuzer/events{/privacy}","received_events_url":"https://api.github.com/users/kaikreuzer/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/eclipse/smarthome/labels/Infrastructure","name":"Infrastructure","color":"bfe5bf"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-12-03T12:41:19Z","updated_at":"2015-12-03T16:20:04Z","closed_at":null,"body":"migrated from Bugzilla [#478597](https://bugs.eclipse.org/bugs/show_bug.cgi?id=478597)\nstatus UNCONFIRMED severity *normal* in component *Infrastructure* for *---*\nReported in version *unspecified* on platform *All*\nAssigned to: Project Inbox\n\nOn 2015-09-29 04:06:10 -0400, Markus Rathgeb wrote:\n\n> Eclipse SmartHome is a framework to build end user solutions on top.\n> \n> If an \"end user\" would like to use that framework an do a release of his software, the software should not depend on a SNAPSHOT at all.\n> \n> The ESH framework themselves is not bound (AFAIK) to any consumer release cycles and this is IMHO fine.\n> \n> But I think it would be fine if we could produce releases from time to time so it could used as a reference for custom products.\n> I cannot depend on 0.8-SNAPSHOT all the time.\n> \n> I do not mean a 1.0 stable framework release without API breaks anymore...\n> I just want to use a fixed reference in my sources.\n> \n> Using custom repositories are possible, but this mean for every reference a new repository. That is not good.\n> \n> If the process for a release is a long task for Eclipse products, I will ask, if we could bump the snapshot version from time to time without a official release.\n> So building a release could build by the consumers.\n> \n> I cannot build a 0.8.0, 0.8.1, ... release myself if Eclipse releases an official 0.8[.0] some time.\n\nOn 2015-09-29 04:39:35 -0400, Kai Kreuzer wrote:\n\n> I agree that fixed releases would definitely help to have a reliable way to reference a  specific code base from within a solution.\n> \n> Note that I am currently preparing the 0.8.0 release, see https://projects.eclipse.org/projects/iot.smarthome/releases/0.8.0/\n> \n> But creating such minor releases is some work; I would not expect more than 2-3 each year.\n> \n> Nonetheless, we could maybe check if we do more regular service releases, which should be a bit simpler (but still means work).\n> We will have to check how much this can be automated (update version in sources, have documentation generated and published, adapt the build plans and download locations etc.)\n\nOn 2015-09-29 04:55:04 -0400, Kai Kreuzer wrote:\n\n> Probably a better option than regular service releases might be to create milestones, e.g. 0.9.0M1, 0.9.0M2 etc. This seems to be possible without following the release process and it I think we also would not need to publish documentation on the website for such milestones.\n\nOn 2015-09-29 07:38:43 -0400, Markus Rathgeb wrote:\n\n> > Probably a better option than regular service releases might be to create\n> > milestones, e.g. 0.9.0M1, 0.9.0M2 etc. This seems to be possible without\n> > following the release process and it I think we also would not need to\n> > publish documentation on the website for such milestones.\n> \n> That would be enough. I just want fixed states we could point to. If this are alphas, betas, release candidates, milestones, releases, ... does not matter for me.\n> As long as it is fixed for a specific code base.\n> \n> If the qualifier (M) is chosen correctly, Maven should handle this correctly, too.\n> https://docs.oracle.com/middleware/1212/core/MAVEN/maven_version.htm#MAVEN400\n\nOn 2015-11-03 12:50:36 -0500, Markus Rathgeb wrote:\n\n> I started doing it for myself:\n> https://github.com/maggu2810/smarthome/commit/SHA: 04f8c9477fb896f77718a377f972f7f91876c639\n> \n> But is there something we can do to get a solution upstream?\n\n"},"comment":{"url":"https://api.github.com/repos/eclipse/smarthome/issues/comments/161701396","html_url":"https://github.com/eclipse/smarthome/issues/612#issuecomment-161701396","issue_url":"https://api.github.com/repos/eclipse/smarthome/issues/612","id":161701396,"user":{"login":"maggu2810","id":204670,"avatar_url":"https://avatars.githubusercontent.com/u/204670?v=3","gravatar_id":"","url":"https://api.github.com/users/maggu2810","html_url":"https://github.com/maggu2810","followers_url":"https://api.github.com/users/maggu2810/followers","following_url":"https://api.github.com/users/maggu2810/following{/other_user}","gists_url":"https://api.github.com/users/maggu2810/gists{/gist_id}","starred_url":"https://api.github.com/users/maggu2810/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/maggu2810/subscriptions","organizations_url":"https://api.github.com/users/maggu2810/orgs","repos_url":"https://api.github.com/users/maggu2810/repos","events_url":"https://api.github.com/users/maggu2810/events{/privacy}","received_events_url":"https://api.github.com/users/maggu2810/received_events","type":"User","site_admin":false},"created_at":"2015-12-03T16:20:04Z","updated_at":"2015-12-03T16:20:04Z","body":"Or we could use a maven plugin that replace a magic string in files in the prepare-packaging phase..."}}