I've prepared issue labels in a test repository. (A test migration is in progress and not yet completed.) https://github.com/mocobeta/sandbox-lucene-10557/issues
Thre are four label families. - type:abcd (Issue Type) - fixVersion:x.x.x (Fix Versions) [1] - affectsVersion:x.x.x (Affects Versions) - component:module/yyyy (Components) If you have any suggestions on label management, please feel free to redesign it. I have no strong opinion on that and may not be able to take the time to think deliberately about it. [1] I first thought of using Milestone for versions, but there were a few questions on it; then I'd keep the current operation: multiple fix versions. 2022年6月20日(月) 19:10 Tomoko Uchida <[email protected]>: > > I haven't used the "project" feature either - maybe it could be an > option but I can't have an opinion on it. Is there anyone who has > experience with it and wants to lead us to use it? > > Tomoko > > 2022年6月20日(月) 18:59 Jens Wille <[email protected]>: > > > > Hi, > > > > I'm just a bystander here. But are you aware that the new projects (beta) > > includes support for custom fields? > > > > <https://docs.github.com/en/issues/trying-out-the-new-projects-experience/creating-a-project#adding-custom-fields> > > > > I haven't used them myself yet, but it seems that they might be a viable > > alternative to modeling everything with labels (which is more of a crutch I > > suppose). > > > > Cheers, > > Jens > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
