-
Notifications
You must be signed in to change notification settings - Fork 92
Maintainer guide
As a maintainer, you should be familiar with the tasks in the Contributor guide.
In addition to primarily monitoring reported issues, and pull requests, you should also monitor the following pieces of infrastructure:
Travis is the continuous integration service. It builds and runs the tests on their infrastructure as described in the .travis.yml located in the project's root directory. The system is run for all new commits to main, on every change to a pull request, or on your personal fork of the repo if you've enabled it.
Is a shared sbt plugin between various core components of the Scala language so that their builds work consistently, have the same publishing settings and metadata, and configure some sbt plugins.
Every so often a new major or minor release of Scala is released. It is worth updating the build for scala-xml to use these new releases. The scala-xml library used to be part of the Scala compiler. Although it is a separate community project now, it is a core part of the Scala ecosystem such that its development still needs to progress in parallel with the compiler.
Lightbend operates a build infrastructure that builds a number of Scala community projects, including the compiler and the scala-xml library. This is a homegrown build system, that is separate from Travis, that is run daily to try and discover integration issues between libraries.
Since the scala-xml is a well-established library, it is important to avoid the risk of changing the source and binary compatability. There is an sbt plugin that can monitor this situation by comparing the current source version with a previous published release of the library. It's called the Migration Manager for Scala.