What about FWH 13.10 and 13.11?

[driessen]

It has been more than 2 months since we had an update of FWH?

I'd like to know what the plans are?

Thanks a lot in advance.

[TimStone]

I was wondering the same thing.

[driessen]

And now I'm wondering why I don't get any answer.

[TimStone]

I do remember a post that said certain solutions were already in 13.10 ... but we never got it.

There were also problems in 13.09 that required Antonio to send us special library builds for xHarbour, but those corrected libraries apparently didn't make it into a 13.09 build.

Apparently everyone is busy ...

[Antonio Linares]

We are delayed for 13.10, but we will publish it next week. Thanks

[Otto]

Hello Antonio,
for my feeling a monthly update is too much.
Maybe you can start poll here.
Best regards,
Otto

[George]

Otto,
I agree with you.
My proposal, as I said before, would be updating FWH every 3 months.
Thus Fivetechsoft has time to develop, test and debug new modules to be included in new FWH versions.

Regards,

George

[Richard Chidiak]

Hello

I also think 1 update fully tested every 3 months is enough

Actually i only update fwh once or twice a year to a max in order to always stabilize a production version

My 2 cents

Richard

[fp]

Two or three updates per year would be enough really. Who installs every month Fivewin update and has the time to test all changes to compatibility with its own programs?

[TimStone]

Quarterly updates would be ok if bug fixes were immediate. There were problems in 13.09 which had fixes for .07 and .08

The repairs never made it into the main build. There were supposed to be fixes in .10 to issues remaining in .09. These are all addressed in various threads.

Microsoft is now on weekly updates. For my clients I do auto updates. Each month there are new features, and bug fixes are immediate. Also important refinements are immediate. Thus I do 3 to 5 updates per month.

With an automated system this is pretty easy. This would be especially helpful with .lib updates.

[HunterEC]

Hi guys:

I think quarterly updates will be ok.

Tim:

Hi, can you post an example of how do you auto update your software ?

Thank you.

[elvira]

Hello!,

I think it´s better few updates but more tested in deep. Latest releases have always bugs, and some important as, for example, the rpreview does not work propelly.

Also, some strings translated into languages are missing, for example.


To see auto update of a programm, see:

http://bielsys.blogspot.com.es/2009/04/ ... ca-de.html

Thanks )

[TimStone]

AUTO UPDATING: I have posted about this before but will re-state here.

There are 3 parts to my updating system. The first is client tracking and payment processing. My system processes payments, then applies them to clients, and creates an encrypted keyfile. This is then uploaded to my server. The keyfile contains the version they are authorized to, which may be in the future. My version numbering system follows the format v:yq:mu, where v is the Version, y is the last digit of the year, q is the quarter of that year, m is the month in that quarter, and u is the update within that month. Thus 6.32.24 would be the 4th update of May, 2013, for Version 6 of the software. When payments are applied, the maximum version allowed is automatically generated and added to the keyfile.

When I complete updates, the version number is set. My management system automatically uploads the update and a version file.

The customer, on their local server, has a program that runs 24/7. Every 3 hours it check my server and download the key file ( just a few seconds ). It also downloads the version file. It checks their current authorization, compares it to what is available on the server, and if there is new software, it downloads it to a folder on the server.

When the customer starts the program, they actually start a routine that checks the local server to see if a newer version is available. If so, it copies it to the workstation first, then starts the program. Otherwise, it just starts the program.

All aspects of this can be fully automated. Credit card payments can be processed online, and if successful, update the main client file.

The auto updater also does other functions. Some files are created and need to be uploaded to 3rd party vendors. This is done automatically, usually sometime after midnight when the system is not being used. Also, it runs an automatic nightly backup. Thirdly, it does an auto email system that sends out notices and reminders to their clients each night when requested. My customer sets it all up once, and then its all automatic.

Tim

[Antonio Linares]

I would propose every two months as once delivered we may need around two weeks for getting feedback and implement fixes.

What do you think about it ? thanks for your feedback

[IBTC]

I would propose every two months

Good solution.