Skip to content

Commit a49ee2c

Browse files
committed
Remove references to the mailing-list
We don't use it anymore.
1 parent 5e325b0 commit a49ee2c

File tree

2 files changed

+0
-2
lines changed

2 files changed

+0
-2
lines changed

CONTRIBUTING.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,6 @@ This is the process for committing code to the Scala project. There are of cours
99
1. Make sure you have signed the [Scala CLA](http://typesafe.com/contribute/cla/scala), if not, sign it.
1010
2. Before starting to work on a feature or a fix, it's good practice to ensure that:
1111
1. There is a ticket for your work in the project's [issue tracker](https://github.com/lampepfl/dotty/issues);
12-
2. If not, create it first (perhaps given a thumbs up from the dotty-internals mailing list first);
1312
2. The ticket has been discussed and prioritized by the team.
1413
3. You should always perform your work in its own Git branch. The branch should be given a descriptive name that explains its intent. Some teams also like adding the ticket number and/or the [GitHub](http://github.com) user ID to the branch name, these details is up to each of the individual teams. (See below for more details on branch naming.)
1514
4. When the feature or fix is completed you should open a [Pull Request](https://help.github.com/articles/using-pull-requests) on GitHub.

README.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,6 @@ Community build: [![Community Build Status](https://travis-ci.org/lampepfl/dotty
77

88
* [Homepage](http://dotty.epfl.ch)
99
* [Documentation](http://dotty.epfl.ch/docs)
10-
* [Mailing list](https://groups.google.com/forum/#!forum/dotty-internals)
1110

1211
Try it out
1312
==========

0 commit comments

Comments
 (0)