We are currently using Varnish 3 which has reached its end-of-life.
We wanted to upgrade to a newer version but when checking the release summary seems all new releases are shown as "retired"
Specifically: https://varnish-cache.org/releases/
Does "retired" mean it should not be used? And if so, which Version is the latest stable release.
Version 4.0 shows as end-of-life, but 4.1 shows as "supported", would this be the latest version for production use?
Varnish 5 was retired and should not be used in production. You can first upgrade your varnish config to 4.x and then use Varnish 6 in production with your 4.x config (it is supported in varnish 6)
Best regards
Related
we have a cassandra node with 3.9 version.
Is it possible to migrate to last stable version (3.0.11)?
(we dont use any special feature of 3.9.)
Please read downgrade session of this guide:
https://wiki.apache.org/cassandra/CompatibilityGuarantees
The main part:
Downgrading is only guaranteed within minor releases and only to the previous bug-fix release
Theoretically you can try downgrading 3.9 -> 3.7 -> 3.5... etc, but there is no grantees that this will work and will not do problems in the future. Test in some dev environment if you have to do it, or stay with 3.9...
I have Critical Updates available on my DNN v06.01.03(108).
AS per Security Center I should get upgraded to 7.4.1.
My Question is - do I need to do upgrade directly to 7.4.1 or in steps?
For e.g. 6.1.3 -> 6.2.9 -> 7.4.1
I would upgrade directly from 6.1.3 to 7.3.4.
Always back up your database and the file system before an upgrade, it is recommended that you do the upgrade in a test environment first, but if you don't have access to a test environment you can always restore to 6.1.3 from your backups if necessary.
Chris
I installed the Achecker from http://www.atutor.ca/achecker/
and ran the guidelines to get a report.
Earlier we were doing the same with http://Achecker.ca
There are few guidelines are missing in the local version. They are not similar. Is there any difference and if yes is there a way to upgrade the techniques to latest on the local version.
The version from the Web site is the Achecker version 1.3 (25/11/2011).
See sourceforge history here:http://sourceforge.net/projects/achecker/files/achecker/
You can find on GitHub, a version of June 2014:
https://github.com/inclusive-design/AChecker
I'm trying to understand restrictions of upgrade from/to different versions of cassandra.
On the one hand, Cassandra docs
http://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgradeC_c.html
are saying "Cassandra 3.0.x restrictions: Upgrade from Cassandra 2.1 versions greater or equal to 2.1.9...", and I understand that as 'you couldn't upgrade to 3.0 from 2.1.8 and prior 2.1.* versions'.
On the other hand, there are no any restrictions on upgrading from, say, 2.1.8 (version prior to 2.1.9) to 2.1.11 (version grater then 2.1.9), in particular, 2.1.8->2.1.11 upgrade don't require upgrade of sstables.
So, could someone explain, why it's possible to upgrade from 2.1.9 to 3.0 but not from 2.1.8 to 3.0?
The docs restrict you from upgrading from early 2.1 versions to 3.0 because there are bug fixes and stability improvements in the later 2.1 releases that affect upgrades.
The best practice is to go to the latest patch on your branch before upgrading a major release. I.E. go to the latest 2.1.x and then go to 3.0.
Note: 3.0.0 dropped last night and it is very early in its release cycle. Make sure you test thoroughly in a qa environment before upgrading your production instance and follow the upgrade docs carefully.
Suppose my extension is version 1.0. I write a new feature and release 1.1. Then I quickly realize I've shipped a bug, fix it, and release 1.2.
Now suppose a user with 1.0 is offline until after 1.2 is released.
Will they update to 1.2 or to 1.1?
Do users get updated to the latest version, or to the next version from the one they have?
Users always get the latest version. So you’ll have to integrate any update code for 1.1 in 1.2 as well.
Every few hours, the browser checks whether any installed extensions or apps have an update URL. For each one, it makes a request to that URL looking for an update manifest XML file. If the update manifest mentions a version that is more recent than what's installed, the browser downloads and installs the new version.
— http://developer.chrome.com/extensions/autoupdate.html