Release Process of wePOS and wePOS Pro

RELEASE.md

wePOS & wePOS Pro Release Process

Step 1: Cloning & Checking out

• Clone the repository, checkout to master. Then checkout again to develop
• git pull for any latest changes

Step 2: Git flow

• Make sure to have git flow installed
• Run git flow init
  • Branch name for production releases: [master]
  • Branch name for "next release" development: [develop]
  • Feature branches? [feature/]
  • Release branches? [release/]
  • Hotfix branches? [hotfix/]
  • Support branches? [support/]
  • Version tag prefix? [] v
• Run git flow release start <version> [ version should be incremented by 1 from the last release ]

Step 3: Change wePOS files

• Change the version, WC tested up to and $version in wepos/wepos.php
• Change the Tested up to, WC tested up to, Stable tag and Changelog in wepos/readme.txt
• Change the Tested up to, WC tested up to, Stable tag and Changelog in wepos/readme.md
• Change the version in wepos/package.json

Step 4: Building and Make zip

• Run npm install
• Run npm run build
• Run npm run zip

Step 5: Get the zip file tested

• The zip should be tested by the QA team

Step 6: Commit the changes after passing QA test

• Run git add .
• Run git commit -m "chore: bump version to <version>"

Step 7: Release

• Run git flow release finish <version>
• Do the vim editor stuff
• Run git push origin develop
• Run git push origin master
• Run git push --tags

Step 8: Update the stable tag

• Draft a new release on GitHub
• Select current tag
• Update changelog
• Attach newly build ZIP file
• Publish the release

Step 4: Building and Make zip for ( Dokan Simple Auction and Dokan WC Booking )

• Run composer install ( No need to run )
• Run npm install
• Run grunt release
• Run grunt zip