• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • What version numbering scheme do people use for their applications and PowerClients?

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved What version numbering scheme do people use for their applications and PowerClients?

  1. Advice
0
Votes
Undo
  1. Daryl Foster
    Daryl Foster
  2. PowerBuilder
  3. Wednesday, 2 February 2022 06:28 AM UTC

Hi Everyone, I'm wondering how everyone uses version numbers in their current applications?  I'm not too far off deploying our first production PowerClient application and thought I would revisit how I version my applications.  Currently I have instance variables in my application manager nvo for version and build number.  I use those version and build numbers to update (manually) the Product Version and File Version when I build an application executable. Now with PowerClient there is also a Deployment Version.  I'm currently not sure how I will use that PowerClient Deployment Version in conjunction with the other version numbers I use. I'd like to know what best practice, or general practice is with versioning applications.  Or alternatively how people are using that PowerClient Deployment Version in their current applications.

Thanks.

  1. Versioning
  2. PowerClient
Cannot connect to the repository (2)
PB 2017 datawindow invalid column name - timestamp
Accepted Answer
Daryl Foster
Daryl Foster Accepted Answer Pending Moderation
  1. Wednesday, 16 February 2022 00:04 AM UTC
  2. PowerBuilder
  3. # Permalink

Thanks for the replies Armeen, Bruce and Ronnie. I've decided to go with Major.Minor.Build

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 16 February 2022 00:23 AM UTC
Sounds good!
  1. Helpful
There are no comments made yet.
Responses (4)
Ronnie Po
Ronnie Po Accepted Answer Pending Moderation
  1. Thursday, 3 February 2022 01:50 AM UTC
  2. PowerBuilder
  3. # 1

We use one additional component compared to Bruce and Armeen:

W.X.Y.Z

W - major release

X - minor release

Y - database compatibility

Z - build number

The Y component is also stored in the database and is used to keep the PB app in sync with compatible database versions. It changes only when there are schema or other changes which make the database incompatible with previous PB code.

 

Comment
Olan Knight
  1. Olan Knight
  2. Thursday, 17 February 2022 19:45 PM UTC
That's the scheme we use,as well.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 2 February 2022 17:53 PM UTC
  2. PowerBuilder
  3. # 2

My suggestion would be increment X.YZ version # as follows:

Increment X when there is new major version of your app.  New major version would be when lots of new features or really big features added or if you upgrade PowerBuilder major versions (e.g. upgrade from 2019 to 2022 for example).

Increment Y when there is new minor version of your app.  New minor version would be when few new features added to your app or upgrade PowerBuilder minor versions (e.g. apply maintenance release to 2019 for example).

Increment Z when maintenance release.  Maintenance release would be when you when you fix bugs in your own code (not bug fixes of PowerBuilder product itself issued by Appeon).

Comment
There are no comments made yet.
Bruce Armstrong
Bruce Armstrong Accepted Answer Pending Moderation
  1. Wednesday, 2 February 2022 23:22 PM UTC
  2. PowerBuilder
  3. # 3

We use something similar to what Armeen recommended:

X.Y.Z

X is year of the major release
Y is the major release number
Z is the minor release number

minor releases are just bug fixes, major releases add significant new features.

We're in agile mode so we do a major release every 3 months and a minor release every month.

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.