Dear #TYPO3 peeps. How likely is it, that you are going to use/ start with v13.0.0 for any serious project?
v13.0 has been released 3 weeks ago and on Packagist, I'm seeing 69 installs (as of now):
https://packagist.org/packages/typo3/cms-core/stats#major/13
v12 LTS has 2.3k installs
https://packagist.org/packages/typo3/cms-core/stats#major/12
v11 LTS has 3.5k installs
https://packagist.org/packages/typo3/cms-core/stats#major/11
v12.0.0 peaked at 134 installs
https://packagist.org/packages/typo3/cms-core/stats#v12.0.0
Wild guess from these numbers: very unlikely…
wdyt?
reshared this
Peter Kraume :typo3:
in reply to Helmut Hummel 🐝 • • •Julian Hofmann
in reply to Helmut Hummel 🐝 • • •@helhum
MarcusSchwemer
in reply to Julian Hofmann • • •Helmut Hummel 🐝
in reply to Julian Hofmann • • •Julian Hofmann
in reply to Helmut Hummel 🐝 • • •No, of course not. Should be a joke...
I agree and was surprised by these numbers :-o
In fact, I don't have any new projects at the moment, only upgrades - and v13 is still too young/unfinished to go live in the next few months or the third extensions are still missing (some even for v12).
@helhum
MarcusSchwemer
in reply to Helmut Hummel 🐝 • • •Peter Kraume :typo3:
in reply to MarcusSchwemer • • •Simon Praetorius
in reply to MarcusSchwemer • • •@MarcusSchwemer Let‘s change that. 😝
I was a bit more conservative in the past. For bigger projects with longer initial development time, I used the latest sprint version. For smaller projects I tended to stick to the latest LTS.
Why? Mostly because of missing 3rd party compatibility (extensions, automating, …).
Simon Praetorius
in reply to Simon Praetorius • • •Albrecht Köhnlein 🚀
in reply to MarcusSchwemer • • •Carsten™
in reply to Albrecht Köhnlein 🚀 • • •still waiting for a job offer then or maybe i'm just one of the odd numbers.
Albrecht Köhnlein 🚀
in reply to Carsten™ • • •@kraehenhuegel Let's try to make a list ...
1) @MarcusSchwemer
2) you
3) @cybersmog
4) me
5) @Xitnelat
6) @helhum
7) @KaffDaddy
... 😂
Albrecht Köhnlein 🚀
in reply to Helmut Hummel 🐝 • • •Rather unlikely.
My project with the most experimental approach always has to wait for Georg Ringer's news.
Stephan Salzmann
in reply to Helmut Hummel 🐝 • • •It depends. As always. But breaking changes during the implementation phase are a problem that the customer would then have to pay for. And so I'm actually always waiting for the LTS release.
But I always play around with the current version and see what has changed and what there is looking forward to.
Daniel Goerz
in reply to Helmut Hummel 🐝 • • •My understanding is that the .0 releases are more useful for extension maintainers than for projects, as projects often need to wait for said extensions to have a compatible release.
While it is cool to hopp onto a new major version early on, it is unlikely to do so for a serious projects that is likely to depend on some existing extensions.
Also, to everyone wondering about the low numbers: those numbers are daily installs and IDK if private packagist installs are included.
Daniel Siepmann likes this.
Julian Hofmann
in reply to Daniel Goerz • • •I can also imagine that in such an early version of v13 - if you are already using it - you are more likely to use the main branch instead of a tagged version.
@ervaude @helhum
Daniel Goerz
in reply to Julian Hofmann • • •@Xitnelat
I think that is even more unlikely, as the main branch is often broken between releases.
I'd not do that. Stick to the releases for projects.
Daniel Siepmann likes this.
Helmut Hummel 🐝
in reply to Daniel Goerz • • •Helmut Hummel 🐝
in reply to Helmut Hummel 🐝 • • •@ervaude And if you only look at the ratio, private packagist installs (which I think still count against public packagist packages afaik), non composer installs or other privately hosted package caches, altogether don't matter as they are evened out.
Unless there is some evidence, that one install type, would prefer either LTS or non LTS versions. I don't think we have such evidence.
Daniel Siepmann likes this.
Daniel Goerz
in reply to Helmut Hummel 🐝 • • •Oh, absolutely there is a meaningful difference.
The main point was, that the dot zero release marks the end of breaking changes and therefore enables extension maintainers to tackle compatibility, so that hopefully, a lot of extensions are compatible when finally the LTS is released, so that serious projects can quickly update and do not have to wait for extension dependencies.
I think most projets update from LTS to LTS, wich is reasonable and fine.
Daniel Goerz
in reply to Daniel Goerz • • •Btw. This is why I think it is a good idea to minimize dependencies to 3rd party extensions.
But every so often this is not feasable, so it is nice that there is enough time for maintainers, at least in theory. :)
Stefan Neufeind
in reply to Helmut Hummel 🐝 • • •Also your numbers only count composer-based installs. For v13 that might pick up, but I've seen quite a number on v11 or v12 as non-composer.
Helmut Hummel 🐝
in reply to Stefan Neufeind • • •@sneufeind see https://chaos.social/@helhum/111971129756532098 regarding non composer installs...
Helmut Hummel 🐝
2024-02-21 19:30:50
Andy
in reply to Helmut Hummel 🐝 • • •Felix
in reply to Helmut Hummel 🐝 • • •