Vignette upgrades are usually not straightforward. You basically have to do a new installation and migrate over all of your customizations etc. Does anyone know if the upcoming V8 version is easier to upgrade or if its easier to upgrade from a certain previous version compared to earlier version. So I can upgrade to an earlier version (say 7.6) and then hopefully its easier?
Vignette v8 is officially not out yet, its only been soft released to some selected clients. My guess is that the upgrade will not be very straightforward but I've no concrete information on that.
During the wait you might also be interested in an open source alternative of Vignette v8 freely available: Sense/Net 6.0 http://blog.sensenet.hu/post/2009/08/05/An-Open-Source-Alternative-for-Vignette-v8.aspx
I have finally found the answer. You do need to upgrade to 7.6 before upgrading to 8.0 from an earlier version.
Related
Is httpclient-4.5.2.jar backward compatible with httpclient-4.3.6.jar?
Same question also for httpcore-4.4.4.jar with httpcore-4.3.3.jar?
I have to use a newer version for supporting some functionality. but is there any impact of my older code?
Is those jar version controlling working conventional way for backward compatibility support like java JDK?
Short answer no. For minor upgrades (4.3.3 to 4.3.4) things usually work, but when you go from 4.3 to 4.5 you can expect changes. See release notes for hints about what you can expect.
Having said that, if you can compile without errors you are usually safe!
We are planning to use Drools in our organisation with Scala/Spark. We have selected Drools Version 5.3.0 and 7.15.0 for our use but we have some stability doubts between them because Version 7.15.0 has recently launched & we are not sure whether it is stable or not.
We have practiced with Version 5.3.0 but we want to know the life cycle of it. What if after some time, Version 5.3.0 will not available for use or some update is brought for this?
So please help us to chose between them which version should we chose for longer use.
Drools 5.3 is outdated version and its not under development. Its better you go with latest release.Drools 7.15 is also stable, but if you are planning to use it for business critical application then I will recommend you to go with enterprise release of Drools 7.x , i.e Red Hat Decision Manager. With enterprise release will get patches for known issue on regular basis and one-off patch for critical issues.
we are going to upgrade our typo3-instance from version 6.1.5 to 7.6. Since we need to clone the instance and afterwards upgrade it in two steps (6.1.5 -> 6.2, 6.2 -> 7.6) we wonder if it was easier to setup a clean 7.6 instance and migrate the data (templates, sites, binaries etc.) afterwards.
There are multiple instruction pages on the web describing how to upgrade to 6.2 and to 7.6 but it seems to be a really tricky process.
So I'd like to know if the t3d data is compatible between those versions. Can we export the data from 6.1.5 and import it to 7.6 without troubles?
What do you think of the approach?
Thanks,
Thomas
So I'd like to know if the t3d data is compatible between those versions. Can we export the data from 6.1.5 and import it to 7.6 without troubles?
Most likely this process will not go without troubles.
Best advice I can give, is to upgrade to 6.2, do the upgrade wizards in the install tool. After that upgrade to 7.6 and do the upgrade wizards in the install tool again (those will be different ones).
Your content should now be fine.
You can keep incompatible extensions uninstalled during this process as it is merely targeting content migration. Don't bother with extension code while doing this. Just the core and your content is enough to provide a working content structure for 7 LTS. Migrate the extensions afterwards.
I prefer the upgrade way to do it, because the t3d export / import thing may work, but may cause some troubles too, especially if this is a bigger site.
If you update the extensions on your 6.2 site to current versions, fix the namespaces and deprecation log entries in your individual extensions, the 6.2. => 7.6 upgrade should be quite smooth. In my experience it is much more convenient than a 4.5 => 6.2 upgrade.
I am upgrading my server from an old version of Mercurial, 1.5 to the newest version. I am wondering if the 2.2 build of Mercurial is stable for use by multiple users at a time. Also are there any gotchas when upgrading like my custom hooks not working, or a buildslave object not working? I have not done a major upgrade on a source control server before so help would be appreciated.
Mercurial is famouse for being very strict regarding compatibility. Have you checked upgrade notes? It list all breaking changes between version. Biggest change for me is introduction of hgweb in 1.6.
Biggest exception from compatibility rules are hooks. Mercurial doesn't guarantee anything so only way is to try.
Also consider making update in two stages. For example first to 1.9 and than to 2.2.
Does anybody know if it's possible to install Typo3 on PHP4? I've looked up the packages-page, but i haven't found anything yet.
Many thanks in regards!
No, it's not possible to install any recent versions. TYPO3 4.6 requires PHP 5.3+ and even TYPO3 4.4 requires PHP 5.2+. Some older versions obviously used to run on PHP 4 but all versions prior to TYPO3 4.4 are outdated, not maintained and insecure.
You do not want PHP4! ;-) a bit sarcastic, but please change your mind / your boss's mind! It's out of support since ages and basically sucks.
I'm sorry, it's not. The system requirements for the latest version state PHP5:
http://typo3.org/about/system-requirements/