[Dune-devel] [Dune] Flyspray turned off
Carsten Gräser
graeser at mi.fu-berlin.de
Mon Nov 2 16:16:11 CET 2015
Hi Steffen,
Am 30.10.2015 um 12:58 schrieb Steffen Müthing:
> Hi everyone,
>
> I’ll start the migration of the Flyspray tasks now. For that purpose, Flyspray will
> be taken offline.
thanks for importing all the old tasks. Now that we have them
in gitlab: How should we proceed using this? Should we use
a) the bug tracker of flyspray/FS for all core modules
b) the per-project bug trackers
in the future/for new bugs.
In case a) the project name 'old flyspray bugs' is misleading
and we should disable the per-project issue trackers. I vaguely
remember that someone said, one can link to bugs in commits via
tagging. Does this still work with a) and how to do this?
Besides this: Are there still automatic notifications via
dune-bugs at ... or do we need to subscribe to tasks manually.
Best,
Carsten
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20151102/4eef7ca7/attachment.sig>
More information about the Dune-devel
mailing list