Testlibrary changes need their own changesets (original) (raw)
Yekaterina Kantserova yekaterina.kantserova at oracle.com
Mon Apr 7 08:49:20 UTC 2014
- Previous message: JDK-8036003: Add variable not to separate debug information.
- Next message: UUID.compareTo broken?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Since the testlibrary exists even in the JDK part I would like to add the Serviceability and Corelibs teams to this discussion.
Thanks, Katja
----- Original Message ----- From: david.holmes at oracle.com To: hotspot-dev at openjdk.java.net Sent: Monday, April 7, 2014 3:50:14 AM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: Testlibrary changes need their own changesets
Unfortunately enhancements to the testlibrary infrastructure code tend to be done in conjunction with the changes to the tests (and sometimes corresponding VM changes) that need the enhancement. This makes it very difficult (sometimes impossible) to backport updates to the testlibrary.
Can I suggest that all updates to the testlibrary classes be done under their own CR (they can still be reviewed alongside the main changes) and committed into a distinct changeset so that they can be readily backported.
Thanks, David
- Previous message: JDK-8036003: Add variable not to separate debug information.
- Next message: UUID.compareTo broken?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]