[Dune] release 2.6

[Steffen Müthing]

Hi Andreas,

sorry for the late reply, the mail somehow slipped through the cracks. I just created
a releases repository in infrastructure. All core developers should have at least
Developer access to it, and I promoted you and Martin to Master access.

Having a central place for bugs etc. is a good idea! In the future (after 2.6) we can also
create a group-level milestone in the Core group (that’s been in GitLab since 9.5), which
should also make it easier to coordinate bug-squashing progress across all the projects.

Steffen

> Am 13.10.2017 um 16:53 schrieb Andreas Dedner <a.s.dedner at warwick.ac.uk>:
> 
> Hi.
> Martin and I want to start with the release process next week. We need a
> place to discuss the open issues, bugs etc. and there was the question
> of helper scripts (I think from Ansgar?) and where to put them. How
> about setting up a project Infrastructure/releases/ with a 2.6 branch.
> The scripts can go into the releases project and discussion on the
> actual release can be done in the issue tracker. Since it is possible to
> link between issues/MR of different project having the discussion for
> all core modules in one place would then be quite easy. I could open up
> an separate issue for each core module in Infrastructure/releases to
> cover discussions on open issues/bugs.
> 
> I don't seam to have permissions to add a project to infrastructures so
> one of the owners would have to start it off.
> Andreas
> 
> 
> 
> _______________________________________________
> Dune mailing list
> Dune at lists.dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <https://lists.dune-project.org/pipermail/dune/attachments/20171017/6102ec48/attachment.sig>