[Development] QtCS: Long Term Release discussion

[rpzrpzrpz at gmail.com]

Don't have the manpower?

Then transfer LTS support over to a group of willing volunteers whose 
businesses depend on it and let them handle as a GROUP the maintenance.

Provide a space on the the Qt Web Site for organizing reasons and make 
it officially a "community" only supported pile of code.

It can even run in parts of the CI that still run it, but keep it 
separate.  Maybe have a part time "maintainer" whose only job is to 
referee group decisions.

That way the rest of the community and the Qt company can advance 
forward and concentrate on future and not legacy and also save precious 
manpower resources for that purpose.

md


On 6/17/2015 11:29 AM, Thiago Macieira wrote:
> On Wednesday 17 June 2015 18:50:14 André Pönitz wrote:
>> Would be possible to freeze 5.6 right now, and release that quickly
>> after 5.5 as LTS, already running on the new CI, and do whatever
>> else was originally planned for 5.6 in 5.7?
>
> I don't think we can do two releases in the next 7 months. We discussed
> shortening release cycles again in QtCS but the conclusion was "let's look
> into this after the new CI is in place".
>
> Anyway, the main point of decision is whether we want an LTS containing stuff
> effectively deprecated. That means maintaining it for a long period, which we
> don't want and don't have the manpower for.
>
> It would be the ideal solution, but I simply don't think we could pull it off.
> Tough luck.
>


-- 
No spell checkers were harmed during the creation of this message.