Trolltech Home | Qt-interest Home | Recent Threads | All Threads | Author | Date
All threads index page 9

Qt-interest Archive, March 2002
RE: Known bugs list (was RE: FileDialog + double click == crash (testcase))

Message 1 in thread

Hi Andy,

Nice to know that Trolltech are listening and are taking some time to
address this issue.

From my viewpoint, I still love Qt.  I belive that our company has
provided you with useful bug reports in both code and documentation to
help make Qt better.  I don't air them in public, they go straight to
qt-bugs.  We don't charge for providing a bug detection service.

What infuriates me right now is the time I waste on reporting bugs that
are supposedly fixed, even to the extent of providing code samples for
you.  If there was a public "change log" or a way to track issues
raised, then my time would be better spent.  That's all I ask, just
something that will help to reduce my time wastage, as I try not to
waste yours.

-- Paul.

> -----Original Message-----
> From: Andy Shaw [mailto:andy@trolltech.com] 
> Sent: 25 March 2002 16:05
> To: qt-interest@trolltech.com
> Subject: Known bugs list (was RE: FileDialog + double click 
> == crash (testcase))
> 
> 
> Since there have been some discussion over the fact that 
> there is no known bugs lists the past few days, I'm here to 
> make an official response on the current situation with this 
> in Trolltech.
> 
> We appreciate your views and we are working on providing 
> something of this nature for the future.  Internal 
> development is taking place for this, and we apologise for 
> any inconvenience caused by the lack of a such system. Please 
> bear with us.
> 
> Thank you for your patience.
> 
> Andy
> ------------------------------------------------
> Mailing Lists Administrator                          Fax: +47 21604801
> Trolltech AS, Waldemar Thranes gt. 98, N-0175 Oslo, Norway
> 
> --
> List archive and information: http://qt-interest.trolltech.com
>
Message 2 in thread

On Mon, 25 Mar 2002, Paul Curtis wrote:

> What infuriates me right now is the time I waste on reporting bugs that
> are supposedly fixed, even to the extent of providing code samples for
> you.  If there was a public "change log" or a way to track issues
> raised, then my time would be better spent.  That's all I ask, just
> something that will help to reduce my time wastage, as I try not to
> waste yours.

FYI, users of the daily snapshots were already able to track the bugfixing
progress during the last weeks as the changes-3.0.3 was updated in the
packages on a weekly basis.

Harri.
Message 3 in thread

Harri,

> > What infuriates me right now is the time I waste on reporting bugs 
> > that are supposedly fixed, even to the extent of providing code 
> > samples for you.  If there was a public "change log" or a 
> way to track 
> > issues raised, then my time would be better spent.  That's 
> all I ask, 
> > just something that will help to reduce my time wastage, as 
> I try not 
> > to waste yours.
> 
> FYI, users of the daily snapshots were already able to track 
> the bugfixing progress during the last weeks as the 
> changes-3.0.3 was updated in the packages on a weekly basis.

That's as may be.  Our company can't get a broadband connection (a
function of where we choose to locate the business), so a 19-22MB
download on a daily/weekly basis over a 64K link, with attendant build
and debug, isn't a viable proposition.  I've already aired my problems
with snapshots...

Still, 3.0.3 is looking quite good (on the plus side), even if it does
leak (we are yet to be proven wrong on this, and await a response in the
fullness of time).

-- Paul.
Message 4 in thread

Paul Curtis <plc@rowley.co.uk> wrote:
>Harri,
>> FYI, users of the daily snapshots were already able to track
>> the bugfixing progress during the last weeks as the
>> changes-3.0.3 was updated in the packages on a weekly basis.
>
>That's as may be.  Our company can't get a broadband connection (a
>function of where we choose to locate the business), so a 19-22MB
>download on a daily/weekly basis over a 64K link, with attendant build
>and debug, isn't a viable proposition.

Same here.

A thought occurs to me...

Each release contains a changes-X.X.X file. If the future contents of 
that file were "drip-fed" to a read-only mailing list between releases 
we would at least know what problems had arisen and been addressed ready 
for the next release. That would go a long way to answering some of the 
queries expressed here. If, where possible and appropriate, diffs were 
included too that would be icing on the cake.

-- 
 [ signature omitted ]
Message 5 in thread

On Mon, Mar 25, 2002 at 05:51:55PM -0000, Paul Curtis wrote:
> Harri,
> 
> > > What infuriates me right now is the time I waste on reporting bugs 
> > > that are supposedly fixed, even to the extent of providing code 
> > > samples for you.  If there was a public "change log" or a 
> > way to track 
> > > issues raised, then my time would be better spent.  That's 
> > all I ask, 
> > > just something that will help to reduce my time wastage, as 
> > I try not 
> > > to waste yours.
> > 
> > FYI, users of the daily snapshots were already able to track 
> > the bugfixing progress during the last weeks as the 
> > changes-3.0.3 was updated in the packages on a weekly basis.
> 
> That's as may be.  Our company can't get a broadband connection (a
> function of where we choose to locate the business), so a 19-22MB
> download on a daily/weekly basis over a 64K link, with attendant build
> and debug, isn't a viable proposition.  I've already aired my problems
> with snapshots...

You could use rsync instead (
http://www.trolltech.com/developer/download/rsync.html ) . The only
problem is that rsync updates usually contain huge changes in the
doc/html subdirectory. But you can just skip that part and just do
(after an initial complete checkout) 'cd $QTDIR/src ; rsync -a
rsync.trolltech.com::qt/src .' for example.


Simon
Message 6 in thread

> On Mon, Mar 25, 2002 at 05:51:55PM -0000, Paul Curtis wrote:

> You could use rsync instead (
> http://www.trolltech.com/developer/download/rsync.html ) . The only
> problem is that rsync updates usually contain huge changes in the
> doc/html subdirectory. But you can just skip that part and just do
> (after an initial complete checkout) 'cd $QTDIR/src ; rsync -a
> rsync.trolltech.com::qt/src .' for example.

According to that page this is for Qt2.x and only for the free edition.

But I would love such a solution for Qt3.x and also for all available
editions. Btw: I would prefer 'CVS' ;-) but could live with rsync too (I
guess ... never tried that tool).

Till then it would be already helpfull if there were a webpage which
announce the changes between the actual snapshot to the latest release. So
everybody could easier decide if it is worth to download the latest
snapshot.

At all I also love, that we'll get a better way to see, which bugs are in,
and already detected.

Great :-)
Message 7 in thread

Hi,

Paul Curtis wrote:

> 
> That's as may be.  Our company can't get a broadband connection (a
> function of where we choose to locate the business), so a 19-22MB
> download on a daily/weekly basis over a 64K link, with attendant build
> and debug, isn't a viable proposition.  I've already aired my problems
> with snapshots...
> 

I agree, having just wasted 90mins trying to download 3.0.3 
before I lost the connection!  Is it not possible to split 
this somehow e.g. strip out the documentation as a separate 
download - has the added advantage that you can take a look 
at whats changed.  The other option would be to provide an 
upgrade from previous release.

Dave
Message 8 in thread

On Tuesday 26 March 2002 12:21, Dave Porritt wrote:
> Hi,
>
> Paul Curtis wrote:
> > That's as may be.  Our company can't get a broadband connection (a
> > function of where we choose to locate the business), so a 19-22MB
> > download on a daily/weekly basis over a 64K link, with attendant build
> > and debug, isn't a viable proposition.  I've already aired my problems
> > with snapshots...
>
> I agree, having just wasted 90mins trying to download 3.0.3
> before I lost the connection!  Is it not possible to split
> this somehow e.g. strip out the documentation as a separate
> download - has the added advantage that you can take a look
> at whats changed.  The other option would be to provide an
> upgrade from previous release.

We are aware of the size of the packages and that this is a problem. We will 
provide (starting with one of the next bugfix releases) also patches towards 
the previous release.

-- 
 [ signature omitted ]
Message 9 in thread

Simon,

> > That's as may be.  Our company can't get a broadband connection (a 
> > function of where we choose to locate the business), so a 19-22MB 
> > download on a daily/weekly basis over a 64K link, with 
> attendant build 
> > and debug, isn't a viable proposition.  I've already aired 
> my problems 
> > with snapshots...
> 
> You could use rsync instead ( 
> http://www.trolltech.com/developer/download/rs> ync.html ) . 
> The only problem is that rsync updates usually 
> contain huge changes in the doc/html subdirectory. But you 
> can just skip that part and just do (after an initial 
> complete checkout) 'cd $QTDIR/src ; rsync -a 
> rsync.trolltech.com::qt/src .' for example.

The other problem is we're using 3.0.3 commercial win, x11, and
embedded.  That is advertised as Qt 2.3 free, something we've never
used.  (Well, we used 2.3 commercial, not 2.3 free).

-- Paul.
Message 10 in thread

Dave:

> Paul Curtis wrote:
> 
> > 
> > That's as may be.  Our company can't get a broadband connection (a 
> > function of where we choose to locate the business), so a 19-22MB 
> > download on a daily/weekly basis over a 64K link, with 
> attendant build 
> > and debug, isn't a viable proposition.  I've already aired 
> my problems 
> > with snapshots...
> > 
> 
> I agree, having just wasted 90mins trying to download 3.0.3 
> before I lost the connection!

We have a rock-solid ISDN connection and it works pretty well
everywhere, and we have ISDN links between our homes and offices.  Done
big downloads.  However, logging on to dist.trolltech.com and trying to
download it with 103 other uses proved unsuccessful.  I eventually
downloaded it about 1am on Monday morning, when I was one of three
users.  I always dread downloading Qt because things just fail if the
server/internet is heavily loaded.

-- Paul.