from pull-request 1416

* refs/heads/fix/markdown-test:
  Fix the failure of MarkdownAppTest

Reviewed-by: 백기선 

CallAction should be called after the app starts.

This test seems to be broken since we start to use play-2.3. I wonder
why this test passed when we used play-2.1.

from pull-request 1404

* refs/heads/issue-1951:
  Fixed a bug for getting notification events

Reviewed-by: 이응준 

from pull-request 1357

* refs/heads/issue-1018:
  add "minLength" option in yobi.ui.Typeahead

Reviewed-by: 채수원 

* ArrayIndexOutOfBoundsException can be occurred if a user's notifications are smaller then
the size of notifications to get.
* This prevents the exception and the user will not see error page.

from pull-request 1377

* refs/heads/upgrade/play-2.3:
  Upgrade Play from 2.2.6 to 2.3.6
  ProjectApp: Fix the incorrect status code for label
  test: Fix url encoding bug
  test: Fix RuntimeExceptions
  Upgrade Play from 2.1.0 to 2.2.6

Reviewed-by: 이희구 

from pull-request 1405

* refs/heads/issue-1965:
  Filtering unauthorzied receivers

Reviewed-by: 이응준 

from pull-request 1409

* refs/heads/issue/authors:
  Authors: Update Authors

Reviewed-by: 이응준 

from pull-request 1414

* refs/heads/github-issue-811:
  ProjectVisitation: Prevented the PersistenceException

Reviewed-by: 채수원 

Related Issue: https://github.com/naver/yobi/issues/811
* By adding constrains, prevent adding duplicated ProjectVisitation data.
* By removing existing duplicated data, users who have duplicated data
can see Project's resources.

from pull-request 1410

* refs/heads/bugfix/label-editor:
  LabelEditor: fix checking a label name has changed

Reviewed-by: 채수원 

Fix a bug that code browser does not show the latest pull request on
each branch.

See https://github.com/naver/yobi/issues/822 for more details about the
issue.

* dythmall-master:
  issue #822 fixed

Reviewed-by: 이응준 

from pull-request 1403

* refs/heads/fix/comment_short_id:
  fix: display comments with short commit-ids

Reviewed-by: 백기선 
Reviewed-by: 이응준 

- Move some commiters to inactive committers.

* Upgrade sbt from 0.13.0 to 0.13.5.
* Upgrade jsmessages from 1.6.1 to 1.6.2.
* Downgrade play-2-mail from 1.0.0 to 0.9.1.
* Split project/Build.scala into build.sbt and
  project/BuildConfig.scala.
* Introduce sbt-less.
* Introduce sbt-twirl, the new template engine for PlayFramework, and
  fix compile errors caused by it.
    * Import scala.collection.JavaConversions._ for conversion between
      Java and Scala collections.
    * Import java.lang_ and java.util._ to use java types.
    * Use implicitJavaLang imported from play.core.j.PlayMagicForJava._
      instead of lang.
    * Use requestHeader imported from play.core.j.PlayMagicForJava._
      instead of request.
    * Specify play.data.Form in full qualified name to avoid conflict
      with play.api.data.Form.
    * Fix the other template errors.
* Etc
    * Use Result instead of deprecated SimpleResult.
    * Use java.nio.file.NotDirectoryException instead of
      scalax.file.NotDirectoryException.
    * Update README to say use "acvitator" command instead of "play".
    * Add methods to PlayServlet to support Servlet 3.1

IMPORTANT NOTE: You should modify the version of h2database on which
Play depends from 1.3.175 to 1.3.176 in
~/.ivy2/cache/com.typesafe.play/play-jdbc_2.10/ivy-2.3.6.xml as follows:

        

to avoid org.h2.jdbc.JdbcSQLException because of the bug that h2database
1.3.175 cannot create or alter sequence.

When a user tries to attach a label to a project, ProjectApp.attachLabel
responses 201 if the label is created newly and attached and 204 if the
label is already attached.

But it shouldn't have work correctly because it was not possible to know
whether the label has been already attached if the label is created just
now. I have no idea why this has worked correctly until I upgrade Play
to 2.2.6.

This also fixes the condition to warn that a label is not attached
abnormaly.

The test failed since Play 2.2.6 is introduced because of encoding
problem that "%2F" is encoded to "%252F" unintetionally in url.

Remove calling routes.ref.Application.init() which causes
"java.lang.RuntimeException: There is no started application".

* Upgrade play-jsmessages from 1.4.1 to 1.6.1
* Use com.fasterxml.jackson.databind.JsonNode instead of
  org.codehaus.jackson.JsonNode;
* Use javassist 3.18.2-GA to fix the verify error
* Use Promise inteadof Result

I consulted docs/ko/Play2.2_Migraion.md

BACKWARD COMPATIBLITY: You should modify the loggers configuration in
conf/application.conf:

    event-handlers = ["akka.event.Logging$DefaultLogger", "akka.event.slf4j.Slf4jEventHandler"]

to:

    loggers = ["akka.event.Logging$DefaultLogger", "akka.event.slf4j.Slf4jLogger"]

A critical security vulnerability of JGit and a bug to check update too
frequently was fixed.

Reviewed-by: insanehong 

from pull-request 1407

* refs/heads/docs/relnotes-0.7.3:
  Add the release note for v0.7.3

Reviewed-by: 김덕홍