From: "Nicolás Ojeda Bär" <nicolas.ojeda.bar@lexifi.com>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] IMPORTANT: Switching from Mantis to GitHub issues on March 14th
Date: Thu, 14 Mar 2019 23:13:07 +0000 [thread overview]
Message-ID: <CADK7aFNBCg5ornCpRn5ZuZfzhvzgnx=EYV1=aS+cPSbry23ukg@mail.gmail.com> (raw)
In-Reply-To: <CADK7aFO-YuYfYdURnEVLbn1mCcj6Gb4b2o_WPO4SN8r0j35+TA@mail.gmail.com>
Dear caml-list,
Thank you for your patience. The migration of the OCaml bug tracker is
now complete.
If you need to report a bug, please do so at
https://github.com/ocaml/ocaml/issues
Note that some of the oldest Mantis issues had to be renumbered. You
can see the full list of renumbered issues here:
https://github.com/ocaml/ocaml/blob/trunk/tools/mantis2gh_stripped.csv
In the coming days, redirections will be put in place so that the old
Mantis URLs will point to the new GitHub ones.
Happy bug reporting!
Best wishes,
Nicolás
on behalf of the OCaml development team
On Wed, Mar 13, 2019 at 12:45 PM Nicolás Ojeda Bär
<nicolas.ojeda.bar@lexifi.com> wrote:
>
> Dear caml-list,
>
> The switch of the OCaml bug tracker from Mantis to GitHub issues will
> take place tomorrow, March 14.
> Mantis will be offline and the GitHub repository will be read-only
> until the migration is finished.
>
> One more e-mail will be sent to this list once the migration is complete.
>
> IMPORTANT: there is still time to send me your Mantis and GitHub user
> names if you want your GitHub user name used in the migrated issues.
>
> Best wishes,
> Nicolás
> on behalf of the OCaml development team
>
> On Mon, Mar 11, 2019 at 11:58 AM Nicolás Ojeda Bär
> <nicolas.ojeda.bar@lexifi.com> wrote:
> >
> > Dear caml-list,
> >
> > We are going to switch the OCaml bug tracker from Mantis to GitHub
> > issues on Thursday, March 14. Existing bug reports will be migrated
> > with the help of a script. On this day, Mantis will be offline and the
> > GitHub repository will be read-only until the migration is finished.
> >
> > A reminder will be sent to this list shortly before the migration.
> >
> > IMPORTANT: if you wish to have the migrated issues use your GitHub
> > user name instead of your Mantis user name, you MUST send me both user
> > names before March 14 so this is taken into account during migration.
> > This may be convenient if you want to be automatically subscribed to
> > issues you authored and/or monitored in Mantis and you do not already
> > subscribe to all GitHub notifications.
> >
> > Do not hesitate to get back to me if you have any questions.
> >
> > Best wishes,
> > Nicolás
> > on behalf of the OCaml development team
next prev parent reply other threads:[~2019-03-14 23:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 10:58 Nicolás Ojeda Bär
2019-03-11 11:06 ` SP
2019-03-11 11:59 ` Nicolás Ojeda Bär
2019-03-11 13:35 ` Yawar Amin
2019-03-11 13:40 ` Sébastien Hinderer
2019-03-11 13:41 ` Nicolás Ojeda Bär
2019-03-11 19:52 ` Yawar Amin
2019-03-13 11:45 ` Nicolás Ojeda Bär
2019-03-14 23:13 ` Nicolás Ojeda Bär [this message]
2019-03-15 8:58 ` Gabriel Scherer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADK7aFNBCg5ornCpRn5ZuZfzhvzgnx=EYV1=aS+cPSbry23ukg@mail.gmail.com' \
--to=nicolas.ojeda.bar@lexifi.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).