Dear Folks @ Apache AGE Community
I would like to initiate this discussion to discuss systematic versioning
of Apache AGE Versioning. Following are my thoughts I would like to
encourage you to provide feedback about this idea as well as give
constructive comments and critics
-
Each branch represents a stable, alpha, beta and RC eg.
-
AGE version 0.6 e.g. AGE_0.6 ALPHA, AGE_0.6_BETA, AGE_0.6_RC
-
AGE version 0.7 e.g. AGE_0.7 ALPHA, AGE_0.7_BETA, AGE_0.7_RC
-
Once a branch reaches at STABLE status alpha, beta and RC branches can
be deleted
-
Each branch can have tags for different PG versions once We start with
PG_11
-
AGE_0.7_ALPHA_PG_11 => AGE Version 0.7 Alpha for PG 11
-
AGE_0.7_ALPHA_PG_12 => AGE Version 0.7 Alpha for PG 12
-
AGE_0.7_BETA_PG_11 => AGE Version 0.7 Alpha for PG 11
-
AGE_0.7_BETA_PG_12 => AGE Version 0.7 Alpha for PG 12
-
AGE_0.7_RC_PG_11 => AGE Version 0.7 Alpha for PG 11
-
AGE_0.7_RC_PG_12 => AGE Version 0.7 Alpha for PG 12
-
AGE_0.7_STABLE_PG_11 => AGE Version 0.7 Alpha for PG 11
-
AGE_0.7_STABLE_PG_12 => AGE Version 0.7 Alpha for PG 12
-
Following rules can be adopted for archiving or depreciating a branch
-
Alpha branch can be archived once Beta branch has been released
-
Beta branch can be archived in favor of a release candidate
-
Release candidate branch achieved in favor of Stable branch
-
A stable branch shall not be architived or depreciated
-
Testing Vs Productions
-
All Alpha, Beta and RC branches shall be used in testing environment
and shall not put into production
-
Users must be informed about the changes in each update including
what it means for them in terms of their current data
-
Users shall be informed about the compatibility between multiple
versions so that they can decide to do an update or not
Thanks and Regards
Shoaib
--
Muhammad *Shoaib, PhD*
Data Scientist, Bioinformatician and AI Engineer
PhD (Biomedical Engineering)
Email: [email protected]
