Page History

...

gradle.properties
1. 1. update versionNumber to the next release version (for example: if you created release branch for 1.8.0 update version number to 1.9.0 in the below files in develop branch)
  2. ensure that releaseType has -SNAPSHOT in it.
geode-core/src/main/java/org/apache/geode/internal/Version.java
1. 1. Add the new ordinal
    Code Block
    language java
    title New ordinal
    //Add 5 to the previous ordinal private static final byte GEODE_190_ORDINAL = 100;
  2. Add the new version
    Code Block
    language java
    title Adding the new version
    public static final Version GEODE_190 = new Version("GEODE", "1.9.0", (byte) 1, (byte) 9, (byte) 0, (byte) 0, GEODE_190_ORDINAL);
  3. Set the current version to the new version
    Code Block
    language java
    title Set current to new version
    public static final Version CURRENT = GEODE_190;
  4. Update the highest version
    Code Block
    language java
    title Set current to new version
    public static final int HIGHEST_VERSION = 105;
geode-core/src/main/java/org/apache/geode/internal/cache/tier/sockets/CommandInitializer.java
1. 1. Add the next version to addCommands
    Code Block
    language java
    title CommandInitializer
    ALL_COMMANDS.put(Version.GEODE_190, commands);
Update the version in geode-book/config.yml on and geode-book/redirects.rb on develop.

Update the expected-pom.xml files

Info

title	Updating the expected-pom files

- build geode after the version is updated in gradle.properties. NOTE:The build will fail but will have the correct pom-default.xml files

Code Block

language	bash
title	gradle build

./gradlew clean build -Dskip.tests=true

- Update dependency versions using gradle task updateExpectedPom.

Code Block

language	bash
title	gradle uEP

./gradlew uEP

- Publish the develop branch to origin

Code Block

title	Publish the release branch

git add .
git commit -a -m "Upgraded version number for releasing 1.x.x"
pit push origin develop

...

Space shortcuts