Skip to content

Commit bf32882

Browse files
committed
Docs on performing a release
1 parent fe28200 commit bf32882

File tree

1 file changed

+23
-1
lines changed

1 file changed

+23
-1
lines changed

README.md

Lines changed: 23 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,29 @@ To build Grails, clone this GitHub repository and execute the install Gradle tar
2424
git clone https://github.com/grails/grails-core.git
2525
cd grails-core
2626
./gradlew install
27-
27+
28+
Performing a Release
29+
---
30+
31+
Releases of Grails are automated by [Travis CI](https://travis-ci.org/grails/grails-core).
32+
33+
To create a release perform the following steps first update the Grails version in `build.gradle` and `grails-core/src/test/groovy/grails/util/GrailsUtilTests.java` then add them to git:
34+
35+
$ git add build.gradle grails-core/src/test/groovy/grails/util/GrailsUtilTests.java
36+
$ git commit -m "Prepare release"
37+
$ git push
38+
39+
After pushing these changes to the repository and wait for the build to complete. During this phase the JAR files will be uploaded to the [Grails Artefactory Repository](https://repo.grails.org/grails/libs-releases-local/).
40+
41+
Once the build completes successfully then tag the release using Git. The tag should begin with the letter 'v'. For example:
42+
43+
$ git tag v3.0.1
44+
$ git push --tags
45+
46+
The tagged release will be automatically uploaded to [Sonatype OSS](https://oss.sonatype.org) and [Github Releases](https://github.com/grails/grails-core/releases).
47+
48+
Although Grails doesn't require the JARs to be in Maven Central for a release, without signing in releasing the staged release via Sonatype OSS the JARs will not be synced to Maven Central.
49+
2850
License
2951
---
3052

0 commit comments

Comments
 (0)