Le mardi 14 janvier 2025, 09:25:55 CET Julien Plissonneau Duquène a écrit :
> Le 2025-01-13 22:23, Gerd Aschemann a écrit :
> > Additionally, I wonder about the technical implementation. Keeping them
> > in one repo on separate branches makes using `repo` real hard.
> > Could we at least combine th
next-release* -> ? (I have no idea)
can stay as is - probably will be one next milestone
waiting-for-feedback -> waiting for-feedback (new label)
new label - I will add
backlog -> delete this milestone and no mapping
drop - no mapping
more-investigation -> more-investigation (new label)
On Tue, 14 Jan 2025 at 09:52, Sandra Parsick wrote:
>
> >
> > I would like to move it to labels.
> > We can use a stale action to close inactive issues, pr.
>
> I found the following milestone in MCLEAN, MJLINK, ARCHETYPE with label
> characteristics (and I give the suggestion, if it was possible
I would like to move it to labels.
We can use a stale action to close inactive issues, pr.
I found the following milestone in MCLEAN, MJLINK, ARCHETYPE with label
characteristics (and I give the suggestion, if it was possible for me,
how to map):
next-release* -> ? (I have no idea)
waiting-
Le 2025-01-13 22:23, Gerd Aschemann a écrit :
Additionally, I wonder about the technical implementation. Keeping them
in one repo on separate branches makes using `repo` real hard.
Could we at least combine them on a single branch? They could have
separate subdirectories, or even a common reacto
