Ok, there are three options I can see and we need to choose one. 1. One add-on for each removed API (e.g. qftp.git, qhttp.git) 2. One add-on for each module (e.g. qt4network.git) 3. A catch-all kitchen sink repository (e.g. qt4support.git)
We promised this when removing the APIs, and again in the Qt5 alpha announcement. The code needs to be available by the time we release the beta. Each API builds as a separate (static) library using only public exports of Qt5. (QHttp has a renamed private copy of QAuthenticator and QRingBuffer) > -----Original Message----- > From: development-bounces+shane.kearns=accenture....@qt-project.org > [mailto:development-bounces+shane.kearns=accenture....@qt-project.org] > On Behalf Of Oswald Buddenhagen > Sent: 29 March 2012 16:48 > To: development@qt-project.org > Subject: Re: [Development] Qftp removal > > On Thu, Mar 29, 2012 at 02:20:04PM +0000, ext > shane.kea...@accenture.com wrote: > > It may not be trivial, but it's the workflow we have defined for > promoting a playground module to an official add-on. > > > yeah. too bad our tool doesn't support that particularly well yet. > > > Would it be any more complex than creating a new project (initialised > > with the contents of the previous project repo, rather than empty) > and > > deleting the old project? > > > deleting projects is not supported, either. every change of structure > will leave a dead repo behind, which clutters up the project overview > (happy admining) and the server. > > > And we've created projects with pre-existing git history before, when > importing the Qt5 modules to gerrit. > > > that's entirely different. they had no previous gerrit history. > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development ________________________________ Subject to local law, communications with Accenture and its affiliates including telephone calls and emails (including content), may be monitored by our systems for the purposes of security and the assessment of internal compliance with Accenture policy. ______________________________________________________________________________________ www.accenture.com _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
