pkg/shelf: spelling fixes

spelling fixes

R=nweiz@google.com

Committed: https://github.com/dart-lang/shelf/commit/57705e17b2b35ba148c6ded0479dc3371c1fb0cf

[kevmoo, 2015-03-24 17:31:25]

kevmoo@google.com changed reviewers:
+ nweiz@google.com

[nweiz, 2015-03-24 20:00:33]

https://codereview.chromium.org/1032623005/diff/1/CHANGELOG.md
File CHANGELOG.md (right):

https://codereview.chromium.org/1032623005/diff/1/CHANGELOG.md#newcode1
CHANGELOG.md:1: ## 0.6.1
This should be 0.6.0+1. 0.6.1 would imply that there are new features.

https://codereview.chromium.org/1032623005/diff/1/pubspec.yaml
File pubspec.yaml (right):

https://codereview.chromium.org/1032623005/diff/1/pubspec.yaml#newcode2
pubspec.yaml:2: version: 0.6.1-dev
Why make this -dev? Unless you have other changes you plan to release very soon,
just release this as 0.6.0+1.

[kevmoo, 2015-03-24 20:03:49]

https://codereview.chromium.org/1032623005/diff/1/CHANGELOG.md
File CHANGELOG.md (right):

https://codereview.chromium.org/1032623005/diff/1/CHANGELOG.md#newcode1
CHANGELOG.md:1: ## 0.6.1
On 2015/03/24 20:00:33, nweiz wrote:
> This should be 0.6.0+1. 0.6.1 would imply that there are new features.

Mapping to pubspec since we can't -dev +1 builds.

See comments on pubspec

https://codereview.chromium.org/1032623005/diff/1/pubspec.yaml
File pubspec.yaml (right):

https://codereview.chromium.org/1032623005/diff/1/pubspec.yaml#newcode2
pubspec.yaml:2: version: 0.6.1-dev
On 2015/03/24 20:00:33, nweiz wrote:
> Why make this -dev? Unless you have other changes you plan to release very
soon,
> just release this as 0.6.0+1.

Because it's not super urgent. For instance, this would go well w/ your pending
patch.

[nweiz, 2015-03-24 20:17:05]

lgtm

https://codereview.chromium.org/1032623005/diff/1/pubspec.yaml
File pubspec.yaml (right):

https://codereview.chromium.org/1032623005/diff/1/pubspec.yaml#newcode2
pubspec.yaml:2: version: 0.6.1-dev
On 2015/03/24 20:03:49, kevmoo wrote:
> On 2015/03/24 20:00:33, nweiz wrote:
> > Why make this -dev? Unless you have other changes you plan to release very
> soon,
> > just release this as 0.6.0+1.
> 
> Because it's not super urgent. For instance, this would go well w/ your
pending
> patch.

Urgency doesn't matter much; it's really easy to release a change, so there's no
reason not to just release every time you make a change unless you're
specifically planning to build on it immediately. Keeping minor improvements
unreleased often means that they just sit and rot in practice.

Since I am about to release another patch, you can keep this as-is if you want,
but for future reference just release.

[kevmoo, 2015-03-24 20:20:33]

On 2015/03/24 20:17:05, nweiz wrote:
> lgtm
> 
> https://codereview.chromium.org/1032623005/diff/1/pubspec.yaml
> File pubspec.yaml (right):
> 
> https://codereview.chromium.org/1032623005/diff/1/pubspec.yaml#newcode2
> pubspec.yaml:2: version: 0.6.1-dev
> On 2015/03/24 20:03:49, kevmoo wrote:
> > On 2015/03/24 20:00:33, nweiz wrote:
> > > Why make this -dev? Unless you have other changes you plan to release very
> > soon,
> > > just release this as 0.6.0+1.
> > 
> > Because it's not super urgent. For instance, this would go well w/ your
> pending
> > patch.
> 
> Urgency doesn't matter much; it's really easy to release a change, so there's
no
> reason not to just release every time you make a change unless you're
> specifically planning to build on it immediately. Keeping minor improvements
> unreleased often means that they just sit and rot in practice.
> 
> Since I am about to release another patch, you can keep this as-is if you
want,
> but for future reference just release.

Understood. Will do.

[kevmoo, 2015-03-24 20:20:49]

Committed patchset #1 (id:1) manually as
57705e17b2b35ba148c6ded0479dc3371c1fb0cf (presubmit successful).