[Dune-devel] [Dune] Flyspray turned off

[Dominic Kempf]

Hey Carsten,

I will gladly spread that information on the mailing list too:

The bugs from the Flyspray bug tracker have been imported into GitLab in
the project flyspray/FS.
You can continue discussion there and reference bugs by writing (That is
why we have chose the group and
repository name as it is):

flyspray/FS#xyz

Please do not open any new bugs in the flyspray project, but instead file
them under the correct core module.
In the long run, it would be nice to squash all those Flyspray bugs.

Concerning mail notifications:

You may set individual notification settings in GitLab. This allows you to
tune your settings this to your needs,
giving different priorities to the core modules etc. If people are
interested we can also maintain the service of
dune-bugs, by having a dummy account in GitLab with the dune-bugs mailing
list as mail address and the correct
notification settings for the core modules. If there is interest in such a
feature, yell, and we will do it.

Best,
Dominic

On Mon, Nov 2, 2015 at 4:32 PM, Carsten Gräser <graeser at mi.fu-berlin.de>
wrote:

> Hi,
> sorry for the noise. It seems that this is all
> answered by Dominics recent commit to  dune-web.
>
> Best,
> Carsten
>
> Am 02.11.2015 um 16:16 schrieb Carsten Gräser:
> > 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
> >
> >
> >
> > _______________________________________________
> > Dune-devel mailing list
> > Dune-devel at dune-project.org
> > http://lists.dune-project.org/mailman/listinfo/dune-devel
> >
>
>
> --
> Prof. Dr. Carsten Gräser
> Freie Universität Berlin
> Institut für Mathematik
> Arnimallee 6
> 14195 Berlin, Germany
> phone: +49 30 838 72637
> fax  : +49 30 838 472637
> email: graeser at mi.fu-berlin.de
> URL  : http://page.mi.fu-berlin.de/graeser
>
>
> _______________________________________________
> Dune-devel mailing list
> Dune-devel at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20151102/81c2c995/attachment.htm>