[Development] Qt infra "weekly" report
Hi State of the CI * Hardware and host wise all seem pretty ok. We had our first host crash in a month sadly. Reported it to Canonical just in case: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814628 * Running network test servers as containers seem to cause such problems that our agent on the VM gets restarted and our state machine doesn't currently like that. We have a fix to handle these situations, but it requires us to recreate our tier1 images with a new bootstrap agent. * Coin on the other hand seems to be suffering from random archive creation problems and what not. Sadly these affect the throughput of the system quite heavily currently. Firewall changes * The changes are almost all done. The next changes that will cause a small maintenance break in the CI will be on week 11. And those changes will be the last ones, and we can then remove the old firewall from the rack. The changes on that week will cause the external IP address of testresults.qt.io to change. Domain name remains the same though. Changes to Coin servers * Coin is currently running on a dedicated hardware using internal SSDs. We now have the capacity to change that so that we use Compellent hard drives. With this move we can start cloning the Coin VM and play around with multiple instances of it if necessary. This is something we will do in the near future, but we haven't decided a specific date for the big move yet. Cheers! -Tony ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Proposal: New branch model
El dom., 10 feb. 2019 05:44, Sune Vuorela escribió: [snip] I'm mostly a casual contributor, mostly dealing with fixes to bugs found > in specific releases. I'm doing my fixes in those releases. Because > that's where I need them. If I could just then push it and more or less > forget about it, that's the thing that would make it easier. > > This seems to me that I need to move the fix forward to dev, then push > it, then backport it. I might not even have a dev build handy. Because > I'm basing my work on top of something released. +1. This is the normal case for distributors (distros) and the patches we normally work on. > ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Proposal: New branch model
On 2019-01-25, Lars Knoll wrote: > * I think it makes the life of casual/new contributors easier. Simply always > develop and push against the development branch. The more experienced > reviewer can then easily decide that the fix should be cherry-picked into a > stable branch. I'm mostly a casual contributor, mostly dealing with fixes to bugs found in specific releases. I'm doing my fixes in those releases. Because that's where I need them. If I could just then push it and more or less forget about it, that's the thing that would make it easier. This seems to me that I need to move the fix forward to dev, then push it, then backport it. I might not even have a dev build handy. Because I'm basing my work on top of something released. /Sune - independent contractor, KDE Developer and Debian Developer ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
