Extract testing utilities into a separate package.

Extract testing utilities into a separate package.

R=brianwilkerson@google.com
BUG=

Committed: https://code.google.com/p/dart/source/detail?r=38039

[Brian Wilkerson, 2014-07-07 20:36:34]

LGTM

[scheglov, 2014-07-07 20:51:13]

Committed patchset #1 manually as r38039 (presubmit successful).

[blois, 2014-07-11 17:38:38]

The versions here seem to be incrementing unusually fast, perhaps you can sync
with Nathan on the versioning strategy?

https://codereview.chromium.org/376693002/diff/1/pkg/analyzer/pubspec.yaml
File pkg/analyzer/pubspec.yaml (right):

https://codereview.chromium.org/376693002/diff/1/pkg/analyzer/pubspec.yaml#ne...
pkg/analyzer/pubspec.yaml:2: version: 0.20.0
I'm curious why the version bump for this?

It looks like 3 version bumps in the same day- perhaps a dev release instead?

[nweiz, 2014-07-11 18:35:41]

On 2014/07/11 17:38:38, blois wrote:
> The versions here seem to be incrementing unusually fast, perhaps you can sync
> with Nathan on the versioning strategy?
> 
> https://codereview.chromium.org/376693002/diff/1/pkg/analyzer/pubspec.yaml
> File pkg/analyzer/pubspec.yaml (right):
> 
>
https://codereview.chromium.org/376693002/diff/1/pkg/analyzer/pubspec.yaml#ne...
> pkg/analyzer/pubspec.yaml:2: version: 0.20.0
> I'm curious why the version bump for this?
> 
> It looks like 3 version bumps in the same day- perhaps a dev release instead?

A few suggestions:

* When iterating quickly on a package, use "-dev" as outlined in this document:
https://docs.google.com/a/google.com/document/d/1kPhEF8rL53S45SpzboyddKW61EUn...

* Keep a CHANGELOG.md file that lists the changes in each release. This helps
users of your package know what they need to change when they upgrade and what
version constraints it's safe to use.

* Don't increment the minor version (or major version for post-1.0.0 packages)
unless you absolutely have to due to public API changes. Doing so causes your
users a lot of pain in version lock and upgrading their own packages. In this
case the only thing that changed were tests, so you should have just added a
build identifier of "+1".

* NEVER EVER release a package with an "any" version constraint. "pub lish"
warns about this for a good reason: the existence of these packages in the repo
can cause very non-local version resolution problems where pub will select them
rather than failing with a useful error message if the user provides invalid
version constraints.

[scheglov, 2014-07-11 19:42:04]

We started actively working on the analysis server and start hitting some
limitations in analyzer.
So, I usually do a fix in the Java code, make a new translation and publish for
using in the server or the services package.

Thank you for reminding me about -dev, I will use it instead.