dosubot[bot] commented on issue #2575:
URL: 
https://github.com/apache/incubator-hugegraph/issues/2575#issuecomment-2220185583

   <!-- Answer -->
   To efficiently prepare for the release of the HugeGraph Distributed 
(pd-store, 1.5) version, you need to address several tasks:
   
   1. **License Issue (#2557):**
      - Review and update dependencies and licenses:
        - **MySQL Connector** - GPL License
        - **word** - GPL License
        - **JBoss Logging 3** - LGPL License
        - **jnr-posix** - LGPL + GPL License
        - **Bootstrap** - MIT License
      - Remove or replace these dependencies to resolve the license issue.
      - Ensure new dependencies comply with licensing requirements by updating 
the `LICENSE` and `NOTICE` files and placing the license files in the 
`./hugegraph-dist/release-docs/licenses/` directory 
<sup>[[1]](https://github.com/apache/incubator-hugegraph/blob/master/.github/outdated/APACHE_PROPOSAL.md)</sup><sup>[[2]](https://github.com/apache/incubator-hugegraph/blob/master/CONTRIBUTING.md)</sup><sup>[[3]](https://github.com/apache/incubator-hugegraph-doc/blob/master/themes/docsy/assets/vendor/bootstrap/scss/bootstrap.scss)</sup>.
   
   2. **pd-store Docker Environment (#2573):**
      - Create a Dockerfile for the pd-store environment. Example:
        ```dockerfile
        FROM ubuntu:latest
   
        # Install JDK 11
        RUN apt-get update && \
            apt-get install -y openjdk-11-jdk maven
   
        # Set environment variables
        ENV USE_STAGE=false
        ENV TRAVIS_DIR=hugegraph-server/hugegraph-dist/src/assembly/travis
        ENV REPORT_DIR=target/site/jacoco
   
        # Copy project files
        COPY . /hugegraph
   
        WORKDIR /hugegraph
   
        # Run Maven package
        RUN mvn clean package -U -Dmaven.javadoc.skip=true 
-Dmaven.test.skip=true -ntp
   
        # Start pd service
        CMD ["sh", "-c", "$TRAVIS_DIR/start-pd.sh"]
        ```
      - Use the `deploy.sh` script to initialize the store and start services:
        ```sh
        cd "${INSTALL_PATH}" || exit
        config_hugegraph_server
        config_hugegraph_studio
   
        "${SERVER_DIR}"/bin/init-store.sh
   
        "${BIN}"/start-all.sh -v "${VERSION}" -p "${INSTALL_PATH}"
        ``` 
<sup>[[4]](https://github.com/apache/incubator-hugegraph-toolchain/blob/master/hugegraph-tools/assembly/bin/deploy.sh)</sup><sup>[[5]](https://github.com/apache/incubator-hugegraph/blob/master/hugegraph-server/Dockerfile)</sup><sup>[[6]](https://github.com/apache/incubator-hugegraph-doc/blob/master/content/en/docs/quickstart/hugegraph-server.md)</sup>.
   
   3. **Miscellaneous Tasks (Issue #2574 and CJK Translation):**
      - Follow specific instructions or requirements mentioned in Issue #2574.
      - Ensure all user-facing text is translated and properly displayed for 
CJK languages.
   
   4. **CI Configuration:**
      - Update the CI configuration in `.github/workflows/pd-store-ci.yml` to 
include necessary steps for testing and packaging. Example snippet:
        ```yml
        name: "hugegraph-pd-store-ci"
   
        on:
          push:
            branches:
              - master
              - 'release-*'
              - 'test-*'
          pull_request:
   
        jobs:
          pd:
            runs-on: ubuntu-latest
            env:
              USE_STAGE: 'false'
              TRAVIS_DIR: hugegraph-server/hugegraph-dist/src/assembly/travis
              REPORT_DIR: target/site/jacoco
   
            steps:
              - name: Install JDK 11
                uses: actions/setup-java@v3
                with:
                  java-version: '11'
                  distribution: 'zulu'
   
              - name: Cache Maven packages
                uses: actions/cache@v3
                with:
                  path: ~/.m2
                  key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }}
                  restore-keys: ${{ runner.os }}-m2
   
              - name: Checkout
                uses: actions/checkout@v4
                with:
                  fetch-depth: 5
   
              - name: use staged maven repo settings
                if: ${{ env.USE_STAGE == 'true' }}
                run: |
                  cp $HOME/.m2/settings.xml /tmp/settings.xml
                  mv -vf .github/configs/settings.xml $HOME/.m2/settings.xml
   
              - name: Package
                run: |
                  mvn clean package -U -Dmaven.javadoc.skip=true 
-Dmaven.test.skip=true -ntp
   
              - name: Run common test
                run: |
                  mvn test -pl hugegraph-pd/hg-pd-test -am -P pd-common-test
   
              - name: Run core test
                run: |
                  mvn test -pl hugegraph-pd/hg-pd-test -am -P pd-core-test
   
              - name: Prepare env and service
                run: |
                  $TRAVIS_DIR/start-pd.sh
   
              - name: Run client test
                run: |
                  mvn test -pl hugegraph-pd/hg-pd-test -am -P pd-client-test
   
              - name: Run rest test
                run: |
                  mvn test -pl hugegraph-pd/hg-pd-test -am -P pd-rest-test
   
              - name: Upload coverage to Codecov
                uses: codecov/[email protected]
                with:
                  file: ${{ env.REPORT_DIR }}/*.xml
        ``` 
<sup>[[7]](https://github.com/apache/incubator-hugegraph/blob/master/.github/workflows/pd-store-ci.yml)</sup>.
   
   By following these steps, you can efficiently prepare for the release of the 
HugeGraph Distributed (pd-store, 1.5) version.
   
   
   <!-- Dosu Comment Footer -->
   *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to