By using this website, you agree to our Terms of Use (click here)
I might regret putting two ideas in one in case one of them gets shot down. Oh well, I've already typed most of this so I'm not turning back at this point 😀
Our current "pre launch" build numbers for AugSQL are 0.1.0, 0.2.0, 0.3.0, etc.
Related to the build numbers, what do you think about keeping the 0.X.X build numbers until we launch to beta testers. The first build for beta testers can be 1.0.0.
Then, when we're ready to launch to the general public, we could have the build number be the earliest version of Acumatica that we're supporting. Since we're supporting the oldest version of Acumatica that is currently supported, we're currently developing on Acumatica 2022 R1 so our first public build number could be 22.1.0. When Acumatica 2022 R2 becomes the oldest supported version, the build number could move to 22.2.0. Thoughts?
On a related note, can we start populating the Build Number in the Description field on the Customization Project? I just tested this and it seems to work. I populated "Build 0.3.1" on the Customization Project like this:
Then I exported and imported the Customization Project to a new Acumatica environment and the Description came along with it which is perfect:
Using the Description field allows the Project Name to stay constant while still informing people of the build that they have installed.
Oh, wait, nevermind, that won't work. When you use ... -> Replace Highlighted Project Content, it's doesn't update the Description. So, nevermind, scratch that idea. I'm preserving the idea here though for posterity.
It would be nice to get the build number in there somehow. Maybe use AugSQL - 0.1.0, AugSQL - 0.2.0, etc. in the Project Name field?
@timrodman piggybacking on Acumatica's version number sounds good at release, we'd then increment each build of our own in the third position sequentially. If we are forced to support multiple versions of Acumatica at the same time (ie. with the upcoming framework changes) this would also seem to support that gracefully.
We went with AugSQL 1.0.0 for the first beta launch version so I'm marking this idea as completed:
