Jump to content

Recommended Posts

For those of us who have been testing the beta, when we receive the 1.7 version on Wednesday, how should we install it on Windows?  I.e. do we do an uninstall of the beta followed by an install of 1.7; or, do we just install 1.7 over the top of the beta??


RickyO
APh and ADe user
New User as of Mar, 2018
Windows10 platform

Share this post


Link to post
Share on other sites

Neither. You install alongside the beta, if it works like all the other Affinity applications work.


-- Walt

Windows 10 Home, version 1903 (18362.356), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.3.481 and 1.8.0.486 Beta   / Affinity Designer 1.7.3.481 and 1.8.0.486 Beta  / Affinity Publisher 1.7.3.481 and 1.8.0.502 Beta

Share this post


Link to post
Share on other sites

Thanks Walt.

I'm just trying to figure out any advantages to retaining the beta.....


RickyO
APh and ADe user
New User as of Mar, 2018
Windows10 platform

Share this post


Link to post
Share on other sites
38 minutes ago, RickyO said:

I'm just trying to figure out any advantages to retaining the beta

There will almost certainly be new betas, perhaps quite quickly to fix any urgent bugs - this is exactly what happened with Designer / Photo going from 1.7 to 1.7.1 in time for the Publisher release.

So if you want to continue testing beta versions, they will install over old Betas and along side the release version.

But it would do no harm to uninstall the beta either!


Win7 Ultimate x64   |   i5-3570K @ 3.4GHz   |   16 GB RAM   |   120 GB SSD   |   nVidia GTX 660 Ti   |   Huion 1060 Plus

How I make GIFs >>> ScreenToGIF (Windows only, Open Source, Portable, ~600kB)

Share this post


Link to post
Share on other sites
3 hours ago, RickyO said:

I'm just trying to figure out any advantages to retaining the beta.....

When there's a new beta, as Aammppaa mentioned, if you've retained the old one your old settings from the prior beta will probably remain in place.

Edit: Actually, that may not be true. The new beta will be a Customer Beta, not a Public Beta as the current one is.

 


-- Walt

Windows 10 Home, version 1903 (18362.356), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.3.481 and 1.8.0.486 Beta   / Affinity Designer 1.7.3.481 and 1.8.0.486 Beta  / Affinity Publisher 1.7.3.481 and 1.8.0.502 Beta

Share this post


Link to post
Share on other sites
3 minutes ago, walt.farrell said:

When there's a new beta, as Aammppaa mentioned, if you've retained the old one your old settings from the prior beta will probably remain in place.

Edit: Actually, that may not be true. The new beta will be a Customer Beta, not a Public Beta as the current one is.

 

Thanks.

But with the release tomorrow, aren't the betas history?  It should be the mark of moving from beta to final.  No?

 


RickyO
APh and ADe user
New User as of Mar, 2018
Windows10 platform

Share this post


Link to post
Share on other sites
3 hours ago, Aammppaa said:

There will almost certainly be new betas, perhaps quite quickly to fix any urgent bugs - this is exactly what happened with Designer / Photo going from 1.7 to 1.7.1 in time for the Publisher release.

So if you want to continue testing beta versions, they will install over old Betas and along side the release version.

But it would do no harm to uninstall the beta either!

Thanks again. 


RickyO
APh and ADe user
New User as of Mar, 2018
Windows10 platform

Share this post


Link to post
Share on other sites
1 hour ago, walt.farrell said:

When there's a new beta, as Aammppaa mentioned, if you've retained the old one your old settings from the prior beta will probably remain in place.

Edit: Actually, that may not be true. The new beta will be a Customer Beta, not a Public Beta as the current one is.

 

Walt, I appreciate your effort.  Unfortunately, I'm even more confused.

Forty years in IT and dev, and the usage of the term beta over the years was consistent and quite different from what Serif is using.  But that's on me.  (We always used alpha, followed by beta, and then onto a final release; with all thereafter being updates, whether minor or major.  This system you're describing is new to me, and seems a bit complicated:  customer beta, public beta, co-existence of beta with final release versions.  Is it just me, or, .....).


RickyO
APh and ADe user
New User as of Mar, 2018
Windows10 platform

Share this post


Link to post
Share on other sites

When Publisher is released, there will be subsequent update releases, which will be released as a „beta“ release before being shipped to the end user. This is not really unusual. Adobe works the same way, Apple with its macOS updates too, and, and, and …

Share this post


Link to post
Share on other sites

Seems overly complicated, especially when put on a timeline.  Too easy to have parallel, out-of-sync versions and dev tracks.  Unnecessary.  Just my experience.


RickyO
APh and ADe user
New User as of Mar, 2018
Windows10 platform

Share this post


Link to post
Share on other sites

Why that? Would you prefer to have no beta release between major editions? If yes, why don‘t you simply renounce on downloading them? You are not forced to do so.

And: Don‘t you think, it is better to expand the base of testing even of dot releases? I think this increases the possibilities of spotting bugs and inconsistencies.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.