From e79cc3ba14a50ba53416d32bee7cd101909dbb7d Mon Sep 17 00:00:00 2001 From: naferx Date: Thu, 28 Jan 2016 09:47:29 -0500 Subject: [PATCH] Update copyright year --- CONTRIBUTING.md | 10 +++++----- LICENSE | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6bdf078ee8..2c1a69ab24 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -96,7 +96,7 @@ For a Pull Request to be considered at all it has to meet these requirements: Other guidelines to follow for copyright notices: - - Use a form of ``Copyright (C) 2011-2015 Typesafe Inc. ``, where the start year is when the project or file was first created and the end year is the last time the project or file was modified. + - Use a form of ``Copyright (C) 2011-2016 Typesafe Inc. ``, where the start year is when the project or file was first created and the end year is the last time the project or file was modified. - Never delete or change existing copyright notices, just add additional info. - Do not use ``@author`` tags since it does not encourage [Collective Code Ownership](http://www.extremeprogramming.org/rules/collective.html). However, each project should make sure that the contributors gets the credit they deserve—in a text file or page on the project website and in the release notes etc. @@ -179,14 +179,14 @@ Example: ## How To Enforce These Guidelines? ### Make Use of Pull Request Validator -Akka uses [Jenkins GitHub pull request builder plugin](https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin) +Akka uses [Jenkins GitHub pull request builder plugin](https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin) that automatically merges the code, builds it, runs the tests and comments on the Pull Request in GitHub. Upon a submission of a Pull Request the Github pull request builder plugin will post a following comment: Can one of the repo owners verify this patch? -This requires a member from a core team to start Pull Request validation process by posting comment consisting only of `OK TO TEST`. +This requires a member from a core team to start Pull Request validation process by posting comment consisting only of `OK TO TEST`. From now on, whenever new commits are pushed to the Pull Request, a validation job will be automaticaly started and the results of the validation posted to the Pull Request. A Pull Request validation job can be started manually by posting `PLS BUILD` comment on the Pull Request. @@ -194,10 +194,10 @@ A Pull Request validation job can be started manually by posting `PLS BUILD` com In order to speed up PR validation times, the Akka build contains a special sbt task called `validatePullRequest`, which is smart enough to figure out which projects should be built if a PR only has changes in some parts of the project. For example, if your PR only touches `akka-persistence`, no `akka-remote` tests need to be run, however the task -will validate all projects that depend on `akka-persistence` (including samples). +will validate all projects that depend on `akka-persistence` (including samples). Also, tests tagged as `PerformanceTest` and the likes of it are excluded from PR validation. -In order to force the `validatePullRequest` task to build the entire project, regardless of dependency analysis of a PRs +In order to force the `validatePullRequest` task to build the entire project, regardless of dependency analysis of a PRs changes one can use the special `PLS BUILD ALL` command (typed in a comment on github, on the Pull Request), which will cause the validator to test all projects. diff --git a/LICENSE b/LICENSE index 0ac6274448..52f688426f 100755 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,6 @@ This software is licensed under the Apache 2 license, quoted below. -Copyright 2009-2015 Typesafe Inc. [http://www.typesafe.com] +Copyright 2009-2016 Typesafe Inc. [http://www.typesafe.com] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of