diff --git a/BreakingChanges.md b/BreakingChanges.md
index f9b008ecfc..8c17daa8ae 100644
--- a/BreakingChanges.md
+++ b/BreakingChanges.md
@@ -2,6 +2,10 @@
 
 ## development HEAD
 
+*None*
+
+## v2503
+
 - The `DTAResolver` and the cli option `--call-graph-analysis=dta` do not work anymore (due to opaque pointers) and will be removed for the next release. Please use the `OTF` or `RTA` resolver instead.
 - The default type-hierarchy implementation has been changed from `LLVMTypeHierarchy` to `DIBasedTypeHierarchy`. This also requires all affected analyses to be performed on LLVM IR that contains debug information.
 - Removed the phasar-library `phasar_controller`. It is now part of the tool `phasar-cli`.
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 91946ef34c..2b8d993810 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -29,7 +29,7 @@ if (NOT PHASAR_IN_TREE)
     DESCRIPTION "A LLVM-based static analysis framework."
   )
 endif ()
-set(PHASAR_VERSION 2403)
+set(PHASAR_VERSION 2503)
 
 # NOTE: When we require cmake >= 3.21, we can use PROJECT_IS_TOP_LEVEL instead
 if (CMAKE_SOURCE_DIR STREQUAL CMAKE_CURRENT_SOURCE_DIR)
diff --git a/README.md b/README.md
index e653aa5260..d15020fae3 100644
--- a/README.md
+++ b/README.md
@@ -5,24 +5,31 @@
 [![C++ Standard](https://img.shields.io/badge/C++_Standard-C%2B%2B17-blue.svg?style=flat&logo=c%2B%2B)](https://isocpp.org/)
 [![GitHub license](https://img.shields.io/badge/license-MIT-blueviolet.svg)](https://raw.githubusercontent.com/secure-software-engineering/phasar/master/LICENSE.txt)
 
-Version 2403
+Version 2503
 
 ## Secure Software Engineering Group
 
 PhASAR is primarily developed and maintained by the Secure Software Engineering Group at Heinz Nixdorf Institute (University of Paderborn) and Fraunhofer IEM.
 
-Lead developers of PhASAR are:  Fabian Schiebel (@fabianbs96)(<fabian.schiebel@iem.fraunhofer.de>), Martin Mory (@MMory)(<martin.mory@upb.de>), Philipp Dominik Schubert (@pdschubert)(<philipp.schubert@upb.de>) and others.
+PhASAR was initially developed by Philipp Dominik Schubert (@pdschubert)(<philipp.schubert@upb.de>).
+
+Currently, PhASAR is maintained by
+- Fabian Schiebel (@fabianbs96)(<fabian.schiebel@iem.fraunhofer.de>)
+- Sriteja Kummita (@sritejakv)
+- Lucas Briese (@jusito)
+- Martin Mory (@MMory)(<martin.mory@upb.de>)
+- *others*
 
 ## Required Version of the C++ Standard
 
-PhASAR requires C++-17.
+PhASAR requires at least C++-17.
 
-However, building in C++20 mode is supported as an experimental feature. You may enable this setting the cmake variable `CMAKE_CXX_STANDARD` to `20`.
+However, building in C++20 mode is supported. You may enable this setting the cmake variable `CMAKE_CXX_STANDARD` to `20`.
 Although phasar currently does not make use of C++-20 features (except for some `concept`s behind an #ifdef border), your client application that just *uses* phasar as a library may want to use C++20 ealier.
 
 ## Currently Supported Version of LLVM
 
-PhASAR is currently set up to support LLVM-14.0.*
+PhASAR is currently set up to support LLVM-15.0.*
 
 ## What is PhASAR?
 
diff --git a/examples/use-phasar-with-fetch-content/CMakeLists.txt b/examples/use-phasar-with-fetch-content/CMakeLists.txt
index cd4d5bb5f2..c6e7ce876c 100644
--- a/examples/use-phasar-with-fetch-content/CMakeLists.txt
+++ b/examples/use-phasar-with-fetch-content/CMakeLists.txt
@@ -12,7 +12,7 @@ include(FetchContent)
 FetchContent_Declare(
   phasar
   GIT_REPOSITORY https://github.com/secure-software-engineering/phasar.git
-  GIT_TAG development # At best, use a tagged version, such as v2403
+  GIT_TAG development # At best, use a tagged version, such as v2503
   EXCLUDE_FROM_ALL
   OVERRIDE_FIND_PACKAGE
 )