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/
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.
Could you please tell me whether do you have releases roadmap? We are waiting for 1.14 - do you have any planned date for this release?
Thanks,
Vadim
I don't think there's an up to date website containing this information, other than the Release Schedule (totally outdated) or Shipping patch Releases (no schedule whatsoever) within the wiki.
That said, the best option at the moment would be to monitor (or directly ask) within the Users or Devs mailing lists (you can subscribe here)
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.
I am confused regarding PostgreSQL BDR and I have several questions:
Question 1: Is BDR truly multi-master for PostgreSQL?
According to the docs here, it says that:
The BDR (Bi-Directional Replication) project adds multi-master
replication to PostgreSQL 9.4
but if I read on 2ndQuadrant, I read the following:
If I read that part, they don't mention multi-master much at all; just that a "second master, working in passive", which indicates its not a real master?
Question 2: Is BDR open-source?
I read here that it is, at least that it was:
BDR is the first open source multi-master replication system for PostgreSQL
Is it still? Because when I look, I am often directed to 2ndQuadrants webpage, and that gives me the impression that its not open-source, when they say that:
How can you get Postgres-BDR?
Just fill out the contact form below and a PostgreSQL expert will be in touch shortly!
Sounds like selling to me =)
Question 3: What version is what?
I read that 2ndQuadrant released version 1.0.5 in March this year. I also read on 2ndQuadrants webpage that
In the complex environment of replication, the 3rd generation of BDR achieves...
The 3rd gen? Is version 1.0.5 that same 3rd gen, or is it something else?
Also, the same page says that:
Note for current Postgres-BDR users: BDR 1.x will reach EOL in December 2019. Our team of PostgreSQL experts can help plan and execute your upgrade with minimal impact and almost zero downtime. Contact us today and a member of our professional services team will be in touch with you as soon as possible.
So, 1.0.5 was released in March, but has EOL in December 2019? Is 2.x not open-source, so some license cost associated with it, and 1.x is EOL 2019?
BDR1 is open source. BDR2 is not. BDR3 is not yet, but should become so at some later stage.
BDR is truly multi-master. The "AlwaysOn Architecture" is a simplified model for BDR deployments that uses active/standby with fast-failover, designed to retain better compatibility with existing applications while improving HA and robustness.
So BDR can and often is deployed in fully multi-master roles, the AlwaysOn architecture just doesn't use it that way.
The BDR 1.x series for PostgreSQL 9.4 (+BDR patches) is open source. It will go EoL in December 2019. It works fine, but I don't recommend it for new deployments given the planned EoL.
The BDR 2.x series (for PostgreSQL 9.6) is not open source and is only available for 2ndQuadrant customers. However, parts of it have been submitted to PostgreSQL itself. It has been superseded by BDR 3.x.
The BDR 3.x series, which is now entering production, is not currently open source and is available only to 2ndQuadrant customers. My understanding is that it's intended for eventual open source release, but no date has been set, and I cannot speak officially for 2ndQuadrant about this. BDR3 adds a much more robust node communication model, better conflict handling, and a lot more, plus it runs on PostgreSQL 10 and 11.
I have been encouraging the relevant people to provide some updated official guidance on these matters. The latest I have for you right now is "News and Roadmap for BDR (Multi-master PostgreSQL)" on the 2ndQuadrant blog.
I received an answer from 2ndQuadrant via email, so I will post it here as it addresses the questions above:
1- "BDR is truly master-master; the shadow master is still a master.
BDR is an eventually consistent multi master solution; in eventually
consistent multi master cluster, it is possible to write on more than
one master at the same time, and conflicts might arise when the same
rows are written at the same time. Conflicts might be acceptable or
not depending on the logical model of the application. Some people do
not need to write on both nodes at the same time, and will use BDR
only to achieve faster failover, as in our BDR-AlwaysOn architecture.
Other people need to write on both nodes, and in that case we need to
assess impact and likeliness of conflicts."
2- BDR 1.x is open source (http://bdr-project.org/docs/stable/) .
Later versions including BDR3 is only available to 2ndQuadrant
Production Support customers. Happy to talk about that in more detail.
You are right, it does sound like selling, we are a business :)
3- The latest version is BDR3, this is the third generation of BDR. It
will still be live, but is only available to Support Customers.
1.x is open source, but EOL as you mentioned.
also, "is only available to Support Customers", meaning it is not a product you can buy one time. You have to pay. Every year. It is a product you rent :( .
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.