{"action":"opened","issue":{"url":"https://api.github.com/repos/elastic/logstash/issues/5151","repository_url":"https://api.github.com/repos/elastic/logstash","labels_url":"https://api.github.com/repos/elastic/logstash/issues/5151/labels{/name}","comments_url":"https://api.github.com/repos/elastic/logstash/issues/5151/comments","events_url":"https://api.github.com/repos/elastic/logstash/issues/5151/events","html_url":"https://github.com/elastic/logstash/issues/5151","id":149919910,"number":5151,"title":"Changes to Logstash build and publish process","user":{"login":"suyograo","id":1595958,"avatar_url":"https://avatars.githubusercontent.com/u/1595958?v=3","gravatar_id":"","url":"https://api.github.com/users/suyograo","html_url":"https://github.com/suyograo","followers_url":"https://api.github.com/users/suyograo/followers","following_url":"https://api.github.com/users/suyograo/following{/other_user}","gists_url":"https://api.github.com/users/suyograo/gists{/gist_id}","starred_url":"https://api.github.com/users/suyograo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/suyograo/subscriptions","organizations_url":"https://api.github.com/users/suyograo/orgs","repos_url":"https://api.github.com/users/suyograo/repos","events_url":"https://api.github.com/users/suyograo/events{/privacy}","received_events_url":"https://api.github.com/users/suyograo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-21T00:09:46Z","updated_at":"2016-04-21T00:09:46Z","closed_at":null,"body":"The goal of this project is to simplify Logstash's build and release process, paving the way for a 1-click release. Today, there are many manual steps which can be error prone. Also the goal is to move from a release snapshot (candidate) to the actual release without making any changes. \r\n\r\nDiscussion from an internal meeting:\r\n\r\n1) Logstash gems (core, event, plugin-api) don't need to line up with Elastic stack release versions\r\n2) Think about possibly making logstash-core not a gem anymore (may impact plugin developers, needs discussion)\r\n3) Logstash internal gems will have a different release cycle from Elastic stack (same way Lucene has a different release cycle from Elasticsearch)\r\n4) Release snapshots do not need to publish any gems\r\n5) Figure out a way to run plugin tests with unpublished logstash-core gems\r\n6) Update our build artifact processes to include more versionable metadata (git hash, build date, build host, etc) so we can differentiate between bug reports in same-versioned internal RCs\r\n\r\n"}}