My team has just upgraded from SpringBoot 1.5.12.RELEASE to 2.4.1 but only to discover that a few days after this major upgrade the documentation references for 2.4.1 have suspiciously and unexpectedly vanished from the documentation page at https://spring.io/projects/spring-boot#learn
We cannot afford that frequent upgrades.
The current GA release is 2.4.2
Why did 2.4.1 disappear?
Was there something fundamentally wrong with 2.4.1 that we should be aware of?
Is there a release plan we can follow going forward?
The Spring project pages only list the most recent patch versions.
I believe this answers my question.
Related
At the company where I am working, there is a huge codebase currently running on Ruby 1.6.8 (2002), which I am tasked with updating to the latest possible version.
There already exists a documentation, which explains how to update the code to Ruby 1.9.3, but even then there is not much documentation which explains the changes which 2.x introduced.
This documentation is also not ideal for me, since it wasn't extensive enough. Is there a website where I can find the changelogs for every Ruby version?
Here https://www.ruby-lang.org/en/downloads/releases/ are the changelogs of each version.
GREENWICH.RELEASE was released by the beginning of this year while SR3 is recently released. Can anyone explain what service release (SR) means? Is it same as SNAPSHOT and will be changed frequently? Or are they fairly stable versions that can be used in a production environment?
An SR means Service Release (subsequent maintenance releases that come after major RELEASE), it's completely stable and can be used on production.
In the project I am working, I have to reuse a project which uses storm 0.9.7.
I do not want to upgrade to higher version as it would need a lot of code changes I I am expected to reuse that code.
Is Storm version 0.9.7 still supported? Or is support for 0.9.7 dropped?
If Storm 0.9.7 is not supported, I may have to rewrite the code
As far as I know development on 0.9.x has stopped. You might still be able to get answers to your questions on the user mailing list, but I'd move to a more recent release.
Im developing a shopping cart system for PyroCMS, but moving my code to 2.2.1 is causing me a few headaches.
I cant find any links that describe the technical changes or how to migrate my existing code over to it.
Is there a public list of technical changes that I can use as a reference?
thanks in advance.
this is the change log, you can take a look at new changes
http://docs.pyrocms.com/2.2/manual/reference/changelog
Upgrade guide from 2.1.x to 2.2.0 (note step 8 for addons)
Upgrade from 2.2.0 to 2.2.1
Essentially 2.1 to 2.2 needs some care, 2.2.0 to 2.2.1 should be a straightforward backup and replace of the system directory if you're not using Git (if you do have the time/ability to learn/use Git, it's hugely beneficial for keeping track of changes).
…and of course always do PyroCMS upgrades on a dev server because it invariably breaks in a way you're not expecting.
Is DWR a dead project? It does not appear to be under active development. The latest 3.0 release appears to be stalled. I'm specifically wondering if there are going to be maintenance releases of DWR 1.x or 2.x or is 3.0 is ever going to be released.
BTW. I asked this question on one of the DWR mailing lists and did not get a response.
Well, the 3.0 version is taking a while to get released, but it is nonetheless very stable.
We are using it in our production environment and we do did encounter any issue so far (2+ years in use).
Important issues on 2.0.X are fixed BTW. (seems that currently there are no major issues on 2.0.X).
BTW. I asked this question on one of the DWR mailing lists and did not get a response.
We had issues before (other version) and those were handler very quick.
Update Dec/2015: V3.0.1 released
Seems like it, I have used DWR like a year back and there is no release since then.
Their version 3 is still on RC (release candidate) and from my understanding of versioning, it is not stable or a general acceptance.
I would say move on... pass DWR. Pass Java too if you can ;)