[TYPO3-core] Proposal for the upcoming Roadmap and LTS

Mario Rimann mario.rimann at typo3.org
Thu Nov 8 17:20:43 CET 2012


Am 08.11.12 15:20, schrieb Jigal van Hemert:
>> With TYPO3 the "remaining maintenance duration" depends on the moment a
>> project is done and which version is used for it as outlined in my
>> previous mail - the customer doesn't always get the same duration of
>> maintenance with his website.
> It's you (or your sales people) who sells the site to your customer. You
> can either do the maintenance yourself or sell a different duration of
> free upgrades to each customer.

Well, I cannot proove it right now, but I remember it differntly: I
remember a typo3.org that exactly advertised that fact of having a long
maintenance period.

We did not sell anything additional to our customers - just mentioned
that TYPO3 will deliver 3+ years maintenance on the LTS version (as
stated on the website). So I don't think we're the ones that sold the
wrong thing or promised too much to happen.

>> I know, and I'm absolutely aware of the workload each additional
>> version brings regarding the maintenance. [...] But I'm asking for a
>> transition path to upgrade from one LTS version to the next LTS
>> version.
> This is the same to me as "I know that each additional version means
> more workload, but I'm still asking you to take more workload".

Then you still get me wrong. I'm just arguing that there is a *need*
from the target audience - and I feel you don't want to hear that and
always respond with "there's no (financial|human) resource to fullfil
this need".

I'm sure we'll be able to find a solution to fill that gap of lacking
resources - but I want the core-team and the "internals" to hear that
there are different needs out there.

> The problem *is* the increased workload compared to the resources we
> have. Please, come up with a solution for that!

That's what I'm trying to accomplish here: Get all facts (which target
audience has which needs), then try to find a solution to satisfy the
needs of as much involved parties as possible.

> If there would be enough people available who are also willing to do a
> lot of backports and test them we can make each release an LTS.

Yes, more power will help - be it financial or human. But on the other
hand just throwing manpower or money onto this issue without having a
plan where and how to collaborate efficiently will waste too much of
those already missing resources IMHO. I hope you understand, why I want
to think and discuss first and then see how we can push things further


More information about the TYPO3-team-core mailing list