Issue tracker

2020-03-06 Thread Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
Hi again.

> At the 2020-Q1 meet-up we decided to use the GitLab issue tracker
> at https://git.lysator.liu.se/pikelang/pike/ for Pike.
>
> Issue numbers were reserved as follows:
>
>   * 1 - 7999  Bugzilla bugs ([Bug ]).
>   *  8000 -   YouTrack issues ([PIKE-]).
>   * 1 -   New (GitLab) issues (#X).
>
> The historic bugs from http://bugzilla.roxen.com/ have now been
> imported (with the same tracking numbers). This means that they
> (well most of them) are publically available again. Note that
> due to the GitLab API used for the import, all issues and comments
> are attributed to Peter Bortas, although the first line of each
> mentions the original commenter.

And now the not quite so old issues from YouTrack have also been
imported. The same attribution issues as with the Bugzilla bugs
also apply here.

/grubba


Issue tracker

2020-03-01 Thread Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
Hi.

At the 2020-Q1 meet-up we decided to use the GitLab issue tracker
at https://git.lysator.liu.se/pikelang/pike/ for Pike.

Issue numbers were reserved as follows:

  * 1 - 7999Bugzilla bugs ([Bug ]).
  *  8000 - YouTrack issues ([PIKE-]).
  * 1 - New (GitLab) issues (#X).

The historic bugs from http://bugzilla.roxen.com/ have now been
imported (with the same tracking numbers). This means that they
(well most of them) are publically available again. Note that
due to the GitLab API used for the import, all issues and comments
are attributed to Peter Bortas, although the first line of each
mentions the original commenter.

/grubba