Re: [Development] abandoning stale changes on gerrit

On 29 Jan 2013, at 8:43 PM, Oswald Buddenhagen wrote: > On Tue, Jan 29, 2013 at 06:43:34PM +, Rutledge Shawn wrote: >> I do actually abandon stuff when it's quite clear that it's dead, but >> due to the review and CI processes, there's quite a large percentage >> of what I write that has hit s

Re: [Development] abandoning stale changes on gerrit

Hi, > > (https://codereview.qt-project.org/#change,46020) > > You are the only one who doesn't like that patch. Otherwise it could have > gone in before Qt 5.0. > > > https://codereview.qt-project.org/#change,39624 > > This patch is the opposite of the previous one, so only one will go in. > Bu

Re: [Development] abandoning stale changes on gerrit

On Wed, Jan 30, 2013 at 11:46:24AM -0800, Alan Alpert wrote: > On Tue, Jan 29, 2013 at 11:43 AM, Oswald Buddenhagen > wrote: > > the cut-off for dead changes will be set at two months (or more - > > tbd) without any activity (which is not pinging). > > Can we please have more specific criteria?

Re: [Development] abandoning stale changes on gerrit

On Thu, Jan 31, 2013 at 10:58:13AM +, Rutledge Shawn wrote: > I question your right to unilaterally decide to put the kibosh on > other people's patches, automatically, across the whole project, even > when they are not on your own review list. > as i stated before, i'm driving forward a proces

Re: [Development] RFC: What constitutes a "non-destabilising" bug-fix?

Hi, I updated https://qt-project.org/wiki/Branch-Guidelines I added the "Where to push a change" section I also added documentation fixes. to the list. On Friday 25 January 2013 09:37:26 Jedrzej Nowacki wrote: > e. Autotests extensions and new tests should go to stable if possible. It > simp

Re: [Development] issue in minimal plugin

On Wednesday 30 January 2013 07:58:25 Thiago Macieira wrote: > On quarta-feira, 30 de janeiro de 2013 17.17.46, Mumtaz Ahmad wrote: > > Hi, > > > > I am trying to run rasterwindow example using minimal plugin but i am > > getting null paint device > > QPainter::begin: Paint device returned engine

Re: [Development] abandoning stale changes on gerrit

On Thursday 31 January 2013 13:08:11 Oswald Buddenhagen wrote: > as i stated before, i'm driving forward a process to decide the > execution details of a previously made decision. Since this decision process has been unnoticed by the people I have asked: Would you mind giving a reference to where

Re: [Development] Closing Jira Bugs

For now I'll go the "add a comment in jira and hope that the assignee closes the task" route.I don't have the privileges to do that myself. However I still like the idea of having an automatic process than scans the commit logs of stable and dev (see Robin's keyword suggestion). Nils

[Development] [Announce] Qt 5.0.1 released

Hi, I'm happy to announce that Qt 5.0.1 is now released. See the blog on http://blog.qt.digia.com/blog/2013/01/31/qt-5-0-1-released/ Thanks go to everybody who has contributed to it! Akseli Salovaara Digia, Qt ___ Announce mailing list annou...@qt-pro

Re: [Development] Danger when excluding auto tests with pre-processor macro.

On Sunday 04 November 2012 12:26:12 Thiago Macieira wrote: > On domingo, 4 de novembro de 2012 10.42.39, Olivier Goffart wrote: > > > At some point Jason McDonald was going over all the tests and fixing > > > this, but maybe someone needs to take a second round now... > > > > I already let Jason k

Re: [Development] [Announce] Qt 5.0.1 released

Hello, Le 31/01/2013 14:10, List for announcements regarding Qt releases and development a écrit : > I'm happy to announce that Qt 5.0.1 is now released. > > See the blog on http://blog.qt.digia.com/blog/2013/01/31/qt-5-0-1-released/ Thanks for the ongoing hard work! Looking at http://qt-projec

Re: [Development] [Announce] Qt 5.0.1 released

Le 31/01/2013 14:28, Yves Bailly a écrit : > Hello, > > Le 31/01/2013 14:10, List for announcements regarding Qt releases and > development a écrit : >> I'm happy to announce that Qt 5.0.1 is now released. >> >> See the blog on http://blog.qt.digia.com/blog/2013/01/31/qt-5-0-1-released/ > > Thanks

Re: [Development] Qt 5.0.0 - feedback on our ways of working

Hi again, I plan to close the survey on Sunday. Hope to see your reply by then. Br, Sinan -Original Message- From: development-bounces+sinan.tanilkan=digia@qt-project.org [mailto:development-bounces+sinan.tanilkan=digia@qt-project.org] On Behalf Of Thiago Macieira Sent: 29. ja

[Development] qt5 bundling harfbuzz

During review for qt5 packaging in fedora, we noticed qt5 includes a bundled copy of harfbuzz in src/3rdparty/harfbuzz/, and there currently doesn't seem to be --system-harfbuzz type build option available. In order to justfify an exception to our usual "no bundled libraries" rule, I would need

Re: [Development] issue in minimal plugin

On 01/31/2013 01:53 PM, Paul Olav Tvete wrote: > On Wednesday 30 January 2013 07:58:25 Thiago Macieira wrote: >> On quarta-feira, 30 de janeiro de 2013 17.17.46, Mumtaz Ahmad wrote: >>> Hi, >>> >>> I am trying to run rasterwindow example using minimal plugin but i am >>> getting null paint device >

[Development] Qt Hebrew

Hello, I would like to initiate a new group called "Qt Hebrew" for Hebrew speakers, where new and potential Hebrew speaking contributors to Qt and to Qt software will be able to join and to share their point of views on translations and report issues concerning to RT

Re: [Development] qt5 bundling harfbuzz

Rex Dieter wrote: > During review for qt5 packaging in fedora, we noticed qt5 includes a > bundled copy of harfbuzz in src/3rdparty/harfbuzz/, and there currently > doesn't seem to be --system-harfbuzz type build option available. svuorela poked me on irc, and seems it's clear now that qt (4 and

Re: [Development] qt5 bundling harfbuzz

On Thu, Jan 31, 2013 at 4:18 PM, Rex Dieter wrote: > Rex Dieter wrote: > >> During review for qt5 packaging in fedora, we noticed qt5 includes a >> bundled copy of harfbuzz in src/3rdparty/harfbuzz/, and there currently >> doesn't seem to be --system-harfbuzz type build option available. > > svuor

Re: [Development] abandoning stale changes on gerrit

On Thu, Jan 31, 2013 at 01:59:17PM +0100, Paul Olav Tvete wrote: > On Thursday 31 January 2013 13:08:11 Oswald Buddenhagen wrote: > > as i stated before, i'm driving forward a process to decide the > > execution details of a previously made decision. > > Since this decision process has been unnoti

Re: [Development] Hebrew and Qt5

hi, On Thu, Jan 31, 2013 at 04:11:43PM +0100, Genghis Khan wrote: > I would like to submit an updated Hebraic translation of Qt 4.x and I > would also like to know how to adjust/update the translation to Qt 5.x. > please follow the instructions on http://qt-project.org/wiki/Qt-Localization (note

Re: [Development] abandoning stale changes on gerrit

On Wednesday 30. January 2013 12.20.18 Oswald Buddenhagen wrote: > On Wed, Jan 30, 2013 at 08:58:32AM +0100, Jedrzej Nowacki wrote: > > Please don't do it. My dashboard contains patches, that I'm interested > > in. It is a kind of knowledge storage, with already signed CLA. I > > understand that a

Re: [Development] abandoning stale changes on gerrit

On Thu, Jan 31, 2013 at 05:26:37PM +0100, Jedrzej Nowacki wrote: > There is no point in closing them either. We aim for time based releases. > There is not need for "prodding". If something is not in then it is for a > future release, or for never, which is also fine. > then call it "reminding",

Re: [Development] abandoning stale changes on gerrit

On 01/31/2013 04:08 AM, Oswald Buddenhagen wrote: > << SNIP >> > > introducing a separate state isn't necessarily a bad idea. > however, from a single user's perspective i don't see a difference to > starring the still relevant changes, and i have doubts that making the > owner's expectations regar

Re: [Development] abandoning stale changes on gerrit

Hi Oswald and others Though I clearly understand the reason, I don't like the idea. It is not that I have a problem with writing 'do not abandon' on my own old changes. My main concern is that we have had contributers who left the community and they have left their patches. Some of these patches

Re: [Development] abandoning stale changes on gerrit

On Thu, Jan 31, 2013 at 3:54 AM, Oswald Buddenhagen wrote: > On Wed, Jan 30, 2013 at 11:46:24AM -0800, Alan Alpert wrote: >> On Tue, Jan 29, 2013 at 11:43 AM, Oswald Buddenhagen >> wrote: >> > the cut-off for dead changes will be set at two months (or more - >> > tbd) without any activity (which

Re: [Development] Danger when excluding auto tests with pre-processor macro.

On 01/31/2013 02:18 PM, Olivier Goffart wrote: > On Sunday 04 November 2012 12:26:12 Thiago Macieira wrote: >> On domingo, 4 de novembro de 2012 10.42.39, Olivier Goffart wrote: At some point Jason McDonald was going over all the tests and fixing this, but maybe someone needs to take a se

Re: [Development] abandoning stale changes on gerrit

On Thu, Jan 31, 2013 at 01:08:11PM +0100, Oswald Buddenhagen wrote: > On Thu, Jan 31, 2013 at 10:58:13AM +, Rutledge Shawn wrote: > > I question your right to unilaterally decide to put the kibosh on > > other people's patches, automatically, across the whole project, even > > when they are not

Re: [Development] abandoning stale changes on gerrit

On Thu, Jan 31, 2013 at 2:58 AM, Rutledge Shawn wrote: > On 29 Jan 2013, at 8:43 PM, Oswald Buddenhagen wrote: > >> On Tue, Jan 29, 2013 at 06:43:34PM +, Rutledge Shawn wrote: >>> I do actually abandon stuff when it's quite clear that it's dead, but >>> due to the review and CI processes, ther

Re: [Development] Danger when excluding auto tests with pre-processor macro.

On Thursday 31 January 2013 20:50:50 Sergio Ahumada wrote: > https://bugreports.qt-project.org/browse/QTBUG-29431 Great :-) > > is this documented somewhere so we don't do this again ? I had modified https://qt-project.org/wiki/Writing_Unit_Tests before I sent the original mail. -- Olivier

Re: [Development] abandoning stale changes on gerrit

On quinta-feira, 31 de janeiro de 2013 17.26.37, Jedrzej Nowacki wrote: > > I was thinking of "withdraw a review", by the contributor, as opposed to > > close > > > it as merged by the CI system. > > > > > > > > But you're right, we need to filter out old junk of rejected reviews. > > There s

Re: [Development] abandoning stale changes on gerrit

On quinta-feira, 31 de janeiro de 2013 19.43.37, Thorbjørn Martsum wrote: > Hi Oswald and others > > Though I clearly understand the reason, I don't like the idea. It is not > that I have a problem with writing 'do not abandon' on my own old changes. > My main concern is that we have had contribute

Re: [Development] abandoning stale changes on gerrit

On Tue, Jan 29, 2013 at 10:43 AM, Rutledge Shawn wrote: > > On 29 Jan 2013, at 1:41 PM, Sorvig Morten wrote: > >> >> On Jan 29, 2013, at 1:05 PM, Oswald Buddenhagen >> wrote: >> >>> moin *, >>> >>> 5.0 is out and the 5.1 feature freeze isn't that far off any more. >>> seems like the best time fo

Re: [Development] Predefined platform dependent constants in QtQuick components

On Tue, Jan 29, 2013 at 9:16 AM, Oleg Shparber wrote: > Hi all, > > During development of the QtQuick2 application for BlackBerry 10 I noticed > that all lists scrolls very quite slow. Same thing with any move of > Flickable's content. The reason is the high resolution of the device's > display. >

[Development] Hi, why I cant login

Hi, since several months ago, I cant login on qt-project web site, I already have an acount but it seems to be blocked or something else. when I try to authenticate the site redirects me to a cute "offline" screen, I wonder if its an acount issue or it's for all the cubans.

[Development] Code Coverage of QtBase - new report available online

Hi, the Qt5 code coverage report is displaying now the code coverage report of the modifications since Qt5.0.0. So for QtBase 3 reports are now online: The actual coverage report of the master branch (computed on a daily basis) The code coverage of Qt5.0.0 (never updated) The code coverage of th

Re: [Development] abandoning stale changes on gerrit

On 01.02.2013 01:37, Alan Alpert wrote: > > That said, I'd prefer it for us to reach a consensus that the > abandoned state should mean abandoned (adj 2 of > http://en.wiktionary.org/wiki/abandoned) instead of destroyed (past > participle of verb 1, http://en.wiktionary.org/wiki/destroy). Then > ab

Re: [Development] abandoning stale changes on gerrit

> > The problem with the original request to simply make all changes > "abandoned" is that it will destroy the differentiation between > "trash" and "not interested in atm". Another problem is that some touches your changes you've invested time and motivation and simply moves it into the trash can