Communicate when a feature by a community contributor will be shipped
- Currently we have not clear process how to put milestones on community contributions.
- For me (Victor W on Plan), I often add the current milestone, assuming the contributor will finish in the current milestone. But often this isn't the case, and I just keep moving the issue along, milestone to milestone.
- This isn't a good communication/expectation for users/customers who actually need the feature. We are not clearly understanding when the feature will be shipped.
- My proposal is that we purposely do not put a milestone on a community contribution issue until the merge request has been merged. We can keep the milestone on the issue to be
Backlog
. In this case, I think it's better to underpromise, since we really have no control of what a community contributor does.
Created this issue after talking with @ja-me-sk in https://gitlab.slack.com/archives/C72HPNV97/p1545157222321400
Edited by Victor Wu