Versions in Aware

BLOMASKY

Wondering how people are using the Versioning which is built into Aware. Here is my question, Yes, it makes sense to create a new version after I publish a live version, but what about during development? Does everyone just stay on V1.1 until they have a product ready to publish? Do you kids create versions at milestones so you can always go back to them or ????

Bruce

kklosson

I only create a version after publishing and I only use major versions. I also maintain a database backup for each version.

BenHayat

BLOMASKY wrote
Wondering how people are using the Versioning which is built into Aware. Here is my question, Yes, it makes sense to create a new version after I publish a live version, but what about during development? Does everyone just stay on V1.1 until they have a product ready to publish? Do you kids create versions at milestones so you can always go back to them or ????

Bruce

Well, I have not "officially" gone to production yet, but during development for the past year and half, I'm still in 1.1. 🙂
But once I go to production, I will follow Aware's versioning.

Markfre1

I create a new mnor version every day or multiple times a day. Even I'm going to do some experimenting or I know the system is really good at a point, I just make a version, so all my experimenting and testing, and if I mess up, just go back and make a new version from the previous. It's doesn't hurt at all, and its like a backup. In addition, sometimes I did something better in an earlier version, so I could go back and looks at what I did, copy, past if needed. At some point, I just start deleting the old versions. Also back up and copy to remote server each day. Works for me.

Mark F.

weblike

Markfre1 wrote
I create a new mnor version every day or multiple times a day. Even I'm going to do some experimenting or I know the system is really good at a point, I just make a version, so all my experimenting and testing, and if I mess up, just go back and make a new version from the previous. It's doesn't hurt at all, and its like a backup. In addition, sometimes I did something better in an earlier version, so I could go back and looks at what I did, copy, past if needed. At some point, I just start deleting the old versions. Also back up and copy to remote server each day. Works for me.

Mark F.

100% same for me. It works.

tford

I develop on my laptop and export BSVs to my local hard drive using a naming sequence that mimics versioning .. it includes date, time and brief mention of major change in that BSV.

I then use "Publish Version" menu option on the server to remotely publish the new version to the server.

Markfre1

Yes. That's one of the benefits. Along the way, I make notes in the BSV of where I left off, and what I am working on in that version. For example, I am experimenting with mobile pick lists. After selecting the Pick list, you then have to enter the Quantity. It was suggested that the pick list, to make it 'in line editing' and add the qty there. One step. Seemed to work but as I tested further there were flaws. So just went back a version and did new and started from there. Did not have to remember all the changes, etc.

Mark F.

BLOMASKY

my problem with MINOR versioning, is that I now have 1.1, 1.2, 1.3...etc. and I am not always that smart to open only the latest one. Is there a way to disable the previous ones/

Bruce

BenHayat

BLOMASKY wrote
my problem with MINOR versioning, is that I now have 1.1, 1.2, 1.3...etc. and I am not always that smart to open only the latest one. Is there a way to disable the previous ones/

Bruce

On the previous ones, Right click and select "Update and unlock". Close IDE, re-open and none of the old ones are even loaded. Saves you memory (if you have anything left) 😃