Skip to content

Deployment

Jump to bottom
Remi Martin edited this page May 30, 2023 · 8 revisions

This guide shows how to deploy and update Piwigo NG on both Play Store and Github.

Requirements

Before we jump to the release process, we need to be sure everything is setup.

Testing

Be sure to test new and old features to avoid bugs on release. Login, upload and navigation are critical features, and must work in any cases.

Version number

Don't forget to increase the app version in the pubspec.yaml

version: a.b.c+abc

How to choose your version name ?

major . minor . hotfix

  • major : Stands for major changes to the application, such as the 2.0.0 which redisigned the app's code ans architecture.
  • minor : A version that added a noticable feature, such as the search page, tags management, ...
  • hotfix : This version includes bug fixing, improvements, and small features.

Once you shoused in hich category your version is, you just need to increment the last version. If you are adding a major or a minor, remember to set lower categories to 0 :

Version is 1.2.8

We add a "minor" update

Version name is now 1.3.0

Now you have your version name, you need to add the version of code.

Build executables

We first need to build the executables:

  • AppBundle for Play Store
  • APK for Github

Github

  • Merge all working branches on Master.

note: Master branch must always compile.

  • Build apk
  • Create a release tag on Master
  • Add apk
  • Write release notes
  • Create release

Testing

Some functionalities are mandatory and must be tested before release. All tests are manual.

  • Login
  • Upload
    • Single file
    • Multiple files
    • Large file
  • Create / Delete album
  • Edit / Move or update / Delete file

Play store

  • Build appBundle
  • Access Piwigo NG console
  • Add appBundle
  • Write release notes
  • Roll out release

Clone this wiki locally