Le jeudi 22 juin 2023 à 14:32 +0200, Jean Abou Samra a écrit : > 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? >
(P.S. For issues, this is different, since some issues should not get a milestone, e.g., issues from before our GitLab migration, and invalid bug reports.)
signature.asc
Description: This is a digitally signed message part
