[Releasing] Duplication of packaging effort

lars.knoll at nokia.com lars.knoll at nokia.com
Tue Aug 14 14:25:07 CEST 2012

On Aug 14, 2012, at 1:15 PM, ext marius.storm-olsen at nokia.com <marius.storm-olsen at nokia.com> wrote:

> On 14/08/2012 01:35, ext Turunen Tuukka wrote:
>> On 14.8.2012 5.46, "jason.mcdonald at nokia.com"
>> <jason.mcdonald at nokia.com> wrote:
>>> I can't see how this duplication of effort is helping us to reach
>>> the Qt5 Beta milestone any quicker (actually quite the opposite
>>> given how few people there seem to be involved with Qt5 packaging),
>>> and we need to get to that milestone before anyone has time to
>>> re-house or make radical changes to the CI infrastructure.
>>> Therefore, we should either
>>> 1) Make both systems generate packages using exactly the same
>>> scripts, configurations and environments (i.e., use copies of the
>>> same VM's), or
>>> 2) Choose one set of packages, test only those, and shut down the
>>> other system because nobody will be doing anything useful with its
>>> output.
>> My preference for #2 - unless we suddenly get a lot more resources to
>> do the testing we would be better off with just one set.
> Ok, let's go for #2 right now, and focus on the packages being generated 
> from the Digia setup right now, until we have the Beta, and possibly the 
> final out.
> However, I still maintain that we _need_ to make this system use the 
> public CI system setup, and it's the only way we can get collaboration 
> on HW platform support.
> As we intend to distribute CI to multiple interested parties, we need to 
> do exactly the same for installer creation and packaging.
> But for now let's focus our resources on one set of results.



More information about the Releasing mailing list