Versions Compared

Old Version 54

changes.mady.by.user Dick Cavender

Saved on

compared with

New Version 55

changes.mady.by.user Dick Cavender

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
titleDiscussion on JIRAs

Send a [DISCUSS] email to dev@geode.apache.org informing developers that a new release branch is about to be created.

Request developers to respond back if they are waiting to finish a JIRA issue, or feel that a particular JIRA / fix must be included in the release.

Request they also confirm that the Geode LICENSE and NOTICE files been confirmed to accurately reflect what is on develop. 

Once this Once the discussion comes to a conclusion and everything that is necessary for the release is present in the develop branch we start with creating the release branch.

...

  1. gradle.properties
      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.
  2. geode-core/src/main/java/org/apache/geode/internal/Version.java

      1. Add the new ordinal

        Code Block
        languagejava
        titleNew ordinal
        //Add 5 to the previous ordinal
private static final byte GEODE_190_ORDINAL = 100;


      2. Add the new version 

        Code Block
        languagejava
        titleAdding 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
        languagejava
        titleSet current to new version
        public static final Version CURRENT = GEODE_190;



      4. Update the highest version

        Code Block
        languagejava
        titleSet current to new version
        public static final int HIGHEST_VERSION = 105;


  3.  geode-core/src/main/java/org/apache/geode/internal/cache/tier/sockets/CommandInitializer.java

      1. Add the next version to addCommands

        Code Block
        languagejava
        titleCommandInitializer 
        ALL_COMMANDS.put(Version.GEODE_190, commands);



  4. Update the version in geode-book/config.yml and geode-book/redirects.rb on develop.

  5. Update the expected-pom.xml files

    Info
    titleUpdating 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
    languagebash
    titlegradle build
    ./gradlew clean build -Dskip.tests=true

    - Update dependency versions using gradle task updateExpectedPom.

    Code Block
    languagebash
    titlegradle uEP
    ./gradlew uEP

    - Publish the develop branch to origin

    Code Block
    titlePublish the release branchchanges to develop
    git add .
git commit -a -m "Upgraded version number for releasing 1.x.x"
pit push origin develop



  6. Update the benchmark baseline to the release branch you just created.

    E.g. in ci/pipelines/shared/jinja.variables.yml around line 59:

    Code Block
    set baseline_branch: "release/1.10.0"
set baseline_version: ""


  7. Update the version in geode-example develop branch.

    Update the version in gradle.properties to the next release's snapshot

    Code Block
    languagebash
    git checkout develop
version = 1.9.0-SNAPSHOT
geodeVersion = 1.9.0-SNAPSHOT
git add -p
git commit
git push origin HEAD


  8. In Jira, add new version of develop: go to https://issues.apache.org/jira/projects/GEODE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page and fill in the new version and click Add.

...