Hello all,
may I ask for a minimal test sequence when you dear AWT/SWING coders
submit/commit a patch for AWT/SWING?
Simply launch the demos in swing and awt and click through to see if
something has changed.
The reason I ask is simple, I often try the included samples from
classpath and see
Hi Andreas, list.
On Wed, 2005-10-05 at 22:08 +0200, Andreas Tobler wrote:
> may I ask for a minimal test sequence when you dear AWT/SWING coders
> submit/commit a patch for AWT/SWING?
Or more automated and requiring less manual effort, a periodic
regression check against mauve?
For example dai
> "Paul" == Paul Jenner <[EMAIL PROTECTED]> writes:
Paul> However I wonder if cross reference against daily mauve regressions
Paul> would help identify and fix these more quickly?
Yes.
The GCC community has a number of auto-builders that send email (using
the ChangeLog) to anybody who breaks
I think, the new list would be ok, because this is a new category of
information. Or maybe the header could have some specific signature
(people receiving many messages per day from several projects use
automated sorting).
IMO it would be very great to get this working.
Tom Tromey wrote:
Pa
I agree a new list is appropriate and that this would be very helpful.
Running the Swing Demo and clicking through everything in there is not
really feasible every time we write a patch. The list would also be
great because when things that were implemented incorrectly break, we
may not know about
5 matches
Mail list logo
