The support times in TYPO3 are "Regular Maintenance", "Priority Bugfixes" and "Extended Support" as you can see in the roadmap: https://typo3.org/cms/roadmap/
What exactly is the difference between the "Priority Bugfixes" and "Extended Support" times?
Is it required to change to the next major version before the "Extended Support" time starts?
Once a LTS release is made, the TYPO3 community / core mergers are fixing bugs for (roughly) 18 months, this also includes security bugfixes - for free.
After that, another 18 months we'll only add important / priority bugfixes. We chose to avoid "important" and used "priority" as everything is important if it is in one persons' project. Anything related to security, browser support or invalid data storage is considered "priority".
Example:
9.5 LTS released in October 2018
Any kind of bugfixes for 18 months (until April 2020)
Any kind of security or browser issues for another 18 months (until October 2021)
Then the official "free" support by the TYPO3 runs out. You can stay on this LTS version, but you might be open for being hacked (however, there are more factors to this than just the LTS version of TYPO3). In any case, no fixes, no releases, no support is given for this version anymore.
You have 3 years of free support with an LTS version.
Extended Support (labelled ELTS) is a special paid offering by TYPO3.com (https://typo3.com/products/extended-support) for projects that cannot (yet) update to the next major. There are usually some external factors related to this (PHP version too old on the servers, no budget for update, relaunch coming the year after). You can find more details on the typo3.com website. I think that one can choose for an ELTS of 1-3 years. This means you can get a total of 6 years of support for an LTS version. Three years for free and up to three additional years by a paid service.
Extended Support can also be an important for larger projects to choose TYPO3 in the beginning so it is ensured (although paid) that support for a long time is given - similar to what Red Hat (RHEL) is offering for their linux distribution.
Regular Maintenance
free of charge
Version is fully supported
18 months (until next LTS release)
Priority Bugfixes
free of charge
Version is supported with security and critical fixes
18 months (until the next but one LTS release)
Extended Support
paid program offered by TYPO3 GmbH
to extend the secure lifetime of a TYPO3 instance
another 36 months
More information
An LTS release of TYPO3 is therefore officially supported 3 years after release. This will be followed by another 3 years in which the support can be purchased from TYPO3 GmbH.
Of course it is always advisable to update after a new LTS release (18 months after LTS release). The next point in time would be the next but one LTS release, since no free support will be offered from this point on (36 months after LTS release). The latest time for an update is the end of Extended Support. (6 years after LTS release)
Of course it is not obligatory to perform the update, but it is advisable for at least security reasons.
Related
We are planning to migrate our old legacy code which uses commons-httpclient-3.x to httpclient5.x . But found that its going to be complete rewrite as lot of classes/packages removed.
Tried migrating to httpclient4.x , seems to be having lesser changes compared to 5.x migration.
But want to know the support plan for 4.x and 5.x from apache/community. As per maven repo, last release on
4.x was on Oct - 2020 where as 5.x was Jan - 2022
Can i expect fixes/code changes in 4.x for the next 4/5 years atleast if i use it instead of 5.x?
Please share if anyone has idea on this.
I posted the same in apache httpclients forum. I got replies.
Reply from 'Oleg' (one of active members in apache httpclient community)
Both branches will continue to be supported, especially 5.1 and 5.2.
The reason for last releases being so far in the past is simply we have
not been getting that many bug reports and there have been no major bug
fixes that would warrant an immediate release.
5.1 and 5.2 releases though can be expected soon.
Can i expect fixes/code changes in 4.x for the next 4/5 years atleast if i use it instead of 5.x?
We are all volunteers here. No one is gets paid for providing
HttpClient support. We can all go away any time. That is the whole
support plan.
One thing I can guarantee however that there will be no feature
development for 4.5 any more. We will likely be doing fixes for severe
and security issues in 4.5 going forward.
Reply from Michael Osipov
At some point in time we need to decide when to cut off 4.x. I don't see
a reason to keep this branch alive for the next five years. Given that
very little work on this project it would make sense to reduce the
amount of supported branches.
Reply from Gary Gregory
The sooner the better for a 4.x cut off IMO. There is a lot of complex code
in total for versions 3, 4, 5, and very limited human resources.
In Short: We can safely migrate to 5.x. I guess this answers for many developers who are looking for an answer like me.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Im trying to find some information about the Cognos analytics but without success.
Im trying to find out what is the latest version of Cognos 11 that is availible and When it was the version released?
How much updates this release have already?
How much bugs were discovered?
Does the upgrade from Cognos 10 to 11 is smooth?
Thanks alot
While the question appears a bit broad, I will try to answer the parts of the question I can understand and, hopefully, it will assist the OP.
These are the approximate release dates for the Cognos Analytics 11 that have been released as of the time of this post:
11.0.0: December 23, 2015
11.0.1: March 29, 2016
11.0.2: May 6, 2016
Interestingly, while the 11.0.1 and 11.0.2 releases are seeming to include fixes only, IBM does not appear to be using Fix Packs in the same way as prior releases of Cognos BI. These are full releases that install and upgrade in the same way as if you were upgrading from BI 10.2.1 to 10.2.2 . There have been at least two interim fixes (IF) released as well, one for 11.0.0 and one for 11.0.2, both related to security, if I recall correctly.
While I don't think there is any official statistic on how many bugs were discovered, fix lists can be found for the released versions here:
11.0.0
11.0.1
11.0.2
The upgrade process from Cognos 10 to 11 is smooth in the sense that the overall process is similar to upgrades in past releases. There are some architectural changes for multi-node environments that change the process for installing subsequent nodes. That said, there are some very important deprecations and feature changes/removals that you will want to learn about, not to mention the new navigation, authoring, and content consumption interfaces.
There are a lot of facets to the release that need considering for any production upgrade -- I would definitely jump into the documentation and, assuming you are a current customer, set up a sandbox to start testing functionality before I made any hard plans for moving a production system forward. If you want more very high level feature discussion, a quick Google search for "Cognos 11 new features" or similar will give you a lot of helpful information.
To follow the announcements on the latest releases, you can subscribe to the IBM Analytics blog:
https://www.ibm.com/communities/analytics/cognos-analytics/blog/
or periodically check the product page:
https://www.ibm.com/analytics/us/en/technology/products/cognos-analytics/
For bug fixes, you should refer to the product release notes:
http://www-01.ibm.com/support/docview.wss?uid=swg27047187
, though the list of bugs seem to be less granular than what you would normally see from other IBM products. The list of bugs does not seem to be broken down by fix pack either.
I do not think the upgrade is a smooth one, since it is not an in-place upgrade like you would have from, let's say, 11.0.1 to 11.0.6. I also could not find a clear statement about the upgrade from 10.x in the installation guide, so it is unclear (for me, as of now) whether the process entails the usual backup of the content manager database from original version and restore the backup image to a new database to be used by the new version
I tried exporting the contents from the 10.x installation via Cognos Admin console and then importing it into the 11.0x release, but 3 out of 5 of my reports simply hang on launch even after performing a report upgrade operation via Admin console.
I'm looking for information regarding Software Collections 2
Is there a release date for version 2?
Will httpd24 also be part of version 2?
Software Collections 2 were released in June. You can see a list of additions here: http://developerblog.redhat.com/2015/04/23/software-collections-2-0-now-beta/
The entire list is here with dates: https://access.redhat.com/support/policy/updates/rhscl
httpd is part of RHSCL 2.
RHSCL has a 3 year lifecycle.
There is no roadmap for SCL and the latest version is 1.2 . The upgrades and updates are on as needed basis by RedHat. The SCL packages are the responsibility of their respective publishers. The httpd24 is up to date and ready to go now and for the foreseeable future.
https://access.redhat.com/documentation/en-US/Red_Hat_Software_Collections/1/html/1.2_Release_Notes/index.html
You can watch HTTPD24 through the issue tracker.
https://www.softwarecollections.org/en/scls/rhscl/httpd24/
I'm trying to select an open BPMN tools for my project,
I found Infinity/Stardust from Eclipse and Activiti.
What are the differences/advantages between these BPMN tools ?
When comparing BPMS one usually needs to consider the particular project requirements and situation. I cannot cover all aspects here, but let me add some thoughts.
A very significant difference between Activiti and Stardust is certainly the size and maturity of the code base. The Stardust code base is more than 5 times the code base of Activiti. Under the hopefully fair assumption that the Stardust team is not coding 5 times less efficiently, Stardust is more feature rich.
Some statistics from Ohloh (#see https://www.ohloh.net/p/eclipse-stardust and https://www.ohloh.net/p/activiti):
Activiti has had 4,388 commits made by 79 contributors representing 438,155 lines of code
Stardust has had 8,312 commits made by 38 contributors representing 2,538,729 lines of code
Activiti took an estimated 116 years of effort (COCOMO model) starting with its first commit in June, 2010 ending with its most
recent commit 3 days ago
Stardust took an estimated 726 years of effort (COCOMO model) starting with its first commit in December, 2011 ending with its most
recent commit 7 days ago
Activiti has a codebase with a long source history maintained by a
very large development team with increasing Y-O-Y commits
Stardust has a young, but established codebase maintained by a
very large development team with stable Y-O-Y commits
Both products originate from the Java world. Activiti seems to keep focusing primarily on the Java community and is sometimes positioned as BPMS for primarily for Java developers. Stardust has invested strongly into interoperability with the .NET world and is also targeting an audience that is not too familiar with Java, for instance with the web modeler. (SunGard has a number of .NET products that it integrates with the commercial Stardust version).
Activiti has a young code base and was designed for BPMN2. Stardust has a 13+ years old code base and is gradually supporting more and more BPMN2 elements.
Greg Harley's comment is not entirely correct.
there is still a commercial product of Stardust, the Infinity Process Platform (IPP). the code bases are synchronized and merged regularly. Both version have no license fees. Support from SunGard is available for the commercial code base. In terms of functionality and maturity Stardust and IPP are almost equivalent.
As a startup CARNOT had its primary market in Germany, Austria and Switzerland and additional traction in the Americas. After the acquisition SunGard rebranded CARNOT to Infinity Process Platform. So it has always been available as a standalone product, recently also hosted and as a Paas/Saas offering. In the Gartner Magic Quadrant 2007 SunGard was ranked 2nd in vision with a strong ability to execute. Later SunGard was not included in the Gartner quadrant anymore because SunGard is primarily offering products to the Finanacial Servcies and Energy industry. IPP is embedded in more than 60 SunGard products and has hundreds of installations worldwide.
Activity has a diverse group of committers and an active community. Some strong contributors like the founder and project lead Tom Baeyens or those from Camunda recently left the Community and started/forked new projects.
Stardust was first release in Summer 2013 in the Eclipse Kepler release. Hence so far its community is young and not very divers at this time. There has been significant growth during the last few months though.
Activiti is under the Apache license. Stardust is under the Eclipse Public License (EPL).
My startup is considering applying for Microsoft BizSpark. I am unclear as to whether or not the software is still usable after 3 years or after the product goes live (whichever comes first). My worry is that we will develop for 2 years, go to production, and all of a sudden we will not be entitled to use the software as the BizSpark agreement will be over. Thank you
After you exit BizSpark, you'll be required to acquire new licenses for any server software you continue to use from Microsoft, that you acquired previously through the program.
After the 3 years when you graduate from the progam, you get licenses for a substantial amount of software, entirely free.
From their FAQ on graduation:
Keep, at no charge, all the software you downloaded during the three
years you were in the BizSpark program. If you have servers in
production, you will get licenses to continue to use up to 4 Windows
Servers (Standard Edition) and 2 SQL Servers (Standard Edition). The
BizSpark team will review requests for startups who need a different
configuration.