On a similar note, the issue workflow will need to be modified if the GitLab tracker is used. Unfortunately, GitLab doesn't seem to have the same functionality as the Launchpad tracker with respect to issue status and severity. This might be a good time to finalize the earlier work that Nick had started to formalize the issue process and the bug tracker workflow before we transition to the GitLab tracker. That way we can define how we want to do this from the outset. This will probably require some trial and error and discussions to fully work it out.
-Ian On Thu, Oct 10, 2019 at 8:51 AM Maciej Suminski <maciej.sumin...@cern.ch> wrote: > On 10/10/19 2:30 AM, Andrew Lutsenko wrote: > <snip> > > In terms of issues migration I think moving open issues via script and > > locking down launchpad tracker is the best option. Even if migrated > > issues and comments on them will be owned by some service account/bot. > > It should be doable to include enough information there so that it's > > clear who originally posted it and the context is not lost. > > I agree, I am not sure if there is any added value in having correct > authors assigned to issues/comments, compared to displaying the > information in the contents field. Since I have spent some time > scripting both Launchpad and Gitlab, let me see how it can be done. > > Cheers, > Orson > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
