{"action":"opened","issue":{"url":"https://api.github.com/repos/aodn/harvesters/issues/183","labels_url":"https://api.github.com/repos/aodn/harvesters/issues/183/labels{/name}","comments_url":"https://api.github.com/repos/aodn/harvesters/issues/183/comments","events_url":"https://api.github.com/repos/aodn/harvesters/issues/183/events","html_url":"https://github.com/aodn/harvesters/issues/183","id":59440786,"number":183,"title":"Could we use issue labels to keep track of harvesters in need of (re-)deployment?","user":{"login":"mhidas","id":3579859,"avatar_url":"https://avatars.githubusercontent.com/u/3579859?v=3","gravatar_id":"","url":"https://api.github.com/users/mhidas","html_url":"https://github.com/mhidas","followers_url":"https://api.github.com/users/mhidas/followers","following_url":"https://api.github.com/users/mhidas/following{/other_user}","gists_url":"https://api.github.com/users/mhidas/gists{/gist_id}","starred_url":"https://api.github.com/users/mhidas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mhidas/subscriptions","organizations_url":"https://api.github.com/users/mhidas/orgs","repos_url":"https://api.github.com/users/mhidas/repos","events_url":"https://api.github.com/users/mhidas/events{/privacy}","received_events_url":"https://api.github.com/users/mhidas/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-02T05:39:09Z","updated_at":"2015-03-02T05:39:09Z","closed_at":null,"body":"It seems like a bit of an inefficient process we go through every iteration: we email Seb or Bene a list of harvesters we want re-depoyed (if we remember them all), he takes it to JPSR, and eventually they make it into an iteration.\r\n\r\nSince every change that requires (re-)deployment of a harvester will have a PR or issue ticket here, couldn't we just have a label like `to_be_deployed` (or `TBD`), which we could add whenever it is ready to be deployed.\r\n\r\nThen, whoever deploys or updates the harvester would remove that tag and instead apply another one, like `in_RC` or `in_production` to indicate where it's been deployed. \r\n\r\nAny thoughts? @pblain @smancini "}}