So far, I think different people have different habits on when to set MR 
milestones — some do it just after merging, some don't, I do it when I remember 
to, and the MRs without milestone get their
milestone on the release day.

Recently, GitLab gained a "bulk edit" button in the MR view. That means the 
person doing the release (currently Jonas) can easily assign all the MRs merged 
during the release in a few clicks, without
having to go through each MR, which reduces the incentive to assign milestones 
manually just after merging. Should we declare having the milestone assigned on 
release as the norm?

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to