BugExplorer: Already fixed in SVN. Please use the forum search before posting bugs.

[Arno.Nyhm]

i read this many times.

Already fixed in SVN. Please use the forum serach before posting bugs.

and there comes ideas to avoid this:


1) give a public access to the gxt commitlog:


like in ExtJS:

Ext JS SVN Commit Log
http://extjs.com/products/extjs/commitlog.php


2) daily updated explorer with a current setup.

like this http://extjs.com/examples/explorer.html but on daily basis

so everybody can see if this is fixed in svn if the error comes not more in the examples explorer


3) BugExplorer

many people post working examples with bugs. so is it possible to place all this examples (with changes) into a BugExplorer - so everybody can play through the bugs and see if it is fixed.

[sven]

1) GXT will also get this public commit log.

2) We already have a dev explorer. It is not updated daily, but from time to time. It is reachable under http://www.extjs.com/examples-dev/ex....html#overview

[Arno.Nyhm]

thx for this link this is very helpful :-)

i think a link to this from the bug guidelines would avoid to many "same bug reportings"

[Colin Alworth]

+1 on the public commit log - even though we have svn access, the comments on most commits are empty, making it hard to see what happens withoudirectly reading the code

[sven]

All new commits have a comment.

[fother]

and about the release cicly?

[Colin Alworth]

All new commits have a comment.

Whoa! I now see that - thanks for the feature I didn't know we had