Prepare to publish analyzer, front_end, and kernel.

Prepare to publish analyzer, front_end, and kernel.

Due to the tight coupling between analyzer and front_end, they need to
be published atomically.  The last published version of kernel is old
enough that it needs to be published too.

I've bumped the versions to the following, and changed the
dependencies so that this set of versions is mutually compatible:

- analyzer: 0.30.0-alpha.3
- front_end: 0.1.0-alpha.2
- kernel: 0.2.0

(Note that kernel's version didn't need bumping since the most
recently published version of it is 0.1.0)

R=asgerf@google.com

Committed: https://github.com/dart-lang/sdk/commit/3dbe0099a249247c14f38301ccf3dfaeee97fe3c

[Paul Berry, 2017-04-21 08:15:58]

paulberry@google.com changed reviewers:
+ asgerf@google.com

[asgerf, 2017-04-21 08:25:56]

LGTM. I have a comment, but I am OK with landing as-is to unblock downstream
users.

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

https://codereview.chromium.org/2828273003/diff/1/pkg/kernel/pubspec.yaml#new...
pkg/kernel/pubspec.yaml:16: test: ^0.12.15+6
Did you check that "pub get" works? 

The test package depends on analyzer, and this dependency usually conflicts with
the -alpha.x version dependency.

Should we just not declare our dev_dependencies in the first place? AFAIK there
is no way to develop kernel outside of the SDK.

[Paul Berry, 2017-04-21 08:34:58]

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

https://codereview.chromium.org/2828273003/diff/1/pkg/kernel/pubspec.yaml#new...
pkg/kernel/pubspec.yaml:16: test: ^0.12.15+6
On 2017/04/21 08:25:56, asgerf wrote:
> Did you check that "pub get" works? 

Unfortunately, due to the tight coupling, there's a chicken-and-egg problem:
"pub get" won't work until after all the related packages are published.  For
instance, if I run it right now in pkg/kernel, it says:

Package analyzer has no versions that match >=0.30.0-alpha.3 <0.31.0 derived
from:
- kernel depends on version ^0.30.0-alpha.3

But that should go away as soon as analyzer is published.

My usual approach is to do my best to get the dependencies right in the first
place, and then if I'm wrong, I bump the versions again and retry.

> The test package depends on analyzer, and this dependency usually conflicts
with
> the -alpha.x version dependency.

Yeah, that's another reason "pub get" isn't going to work, even after
publishing.  Usually what we do is ask Bob to widen test's dependency on
analyzer after publishing, at which point things start working because now there
is a version of test out there that satisfies the constraints.

> Should we just not declare our dev_dependencies in the first place? AFAIK
there
> is no way to develop kernel outside of the SDK.

That's a really good point.  I'll open up an email discussion about that.

[Paul Berry, 2017-04-21 08:35:40]

Description was changed from

==========
Prepare to publish analyzer, front_end, and kernel.

Due to the tight coupling between analyzer and front_end, they need to
be published atomically.  The last published version of kernel is old
enough that it needs to be published too.

I've bumped the versions to the following, and changed the
dependencies so that this set of versions is mutually compatible:

- analyzer: 0.30.0-alpha.3
- front_end: 0.1.0-alpha.2
- kernel: 0.2.0

(Note that kernel's version didn't need bumping since the most
recently published version of it is 0.1.0)
==========

to

==========
Prepare to publish analyzer, front_end, and kernel.

Due to the tight coupling between analyzer and front_end, they need to
be published atomically.  The last published version of kernel is old
enough that it needs to be published too.

I've bumped the versions to the following, and changed the
dependencies so that this set of versions is mutually compatible:

- analyzer: 0.30.0-alpha.3
- front_end: 0.1.0-alpha.2
- kernel: 0.2.0

(Note that kernel's version didn't need bumping since the most
recently published version of it is 0.1.0)

R=asgerf@google.com

Committed:
https://github.com/dart-lang/sdk/commit/3dbe0099a249247c14f38301ccf3dfaeee97fe3c
==========

[Paul Berry, 2017-04-21 08:35:41]

Committed patchset #1 (id:1) manually as
3dbe0099a249247c14f38301ccf3dfaeee97fe3c (presubmit successful).

[Paul Berry, 2017-04-21 08:57:22]

On 2017/04/21 08:34:58, Paul Berry wrote:
> https://codereview.chromium.org/2828273003/diff/1/pkg/kernel/pubspec.yaml
> File pkg/kernel/pubspec.yaml (right):
> 
>
https://codereview.chromium.org/2828273003/diff/1/pkg/kernel/pubspec.yaml#new...
> pkg/kernel/pubspec.yaml:16: test: ^0.12.15+6
> On 2017/04/21 08:25:56, asgerf wrote:
> > Should we just not declare our dev_dependencies in the first place? AFAIK
> there
> > is no way to develop kernel outside of the SDK.
> 
> That's a really good point.  I'll open up an email discussion about that.

On further reflection, I think that front_end and analyzer also only make sense
to develop within the SDK.  So we don't really need to worry about having a set
of mutually compatiable versions listed in dev_dependencies, because no one is
going to run "pub get" in one of these directories and expect to be able to do
development work.

However, I think listing the dev_dependencies is still useful documentation, and
it has the nice effect of suppressing annoying warnings from "pub publish".  So
I think I'll go ahead and leave the dependencies in place.

[Siggi Cherem (dart-lang), 2017-04-21 16:12:59]

On 2017/04/21 08:57:22, Paul Berry wrote:
> On 2017/04/21 08:34:58, Paul Berry wrote:
> > https://codereview.chromium.org/2828273003/diff/1/pkg/kernel/pubspec.yaml
> > File pkg/kernel/pubspec.yaml (right):
> > 
> >
>
https://codereview.chromium.org/2828273003/diff/1/pkg/kernel/pubspec.yaml#new...
> > pkg/kernel/pubspec.yaml:16: test: ^0.12.15+6
> > On 2017/04/21 08:25:56, asgerf wrote:
> > > Should we just not declare our dev_dependencies in the first place? AFAIK
> > there
> > > is no way to develop kernel outside of the SDK.
> > 
> > That's a really good point.  I'll open up an email discussion about that.
> 
> On further reflection, I think that front_end and analyzer also only make
sense
> to develop within the SDK.  So we don't really need to worry about having a
set
> of mutually compatiable versions listed in dev_dependencies, because no one is
> going to run "pub get" in one of these directories and expect to be able to do
> development work.
> 
> However, I think listing the dev_dependencies is still useful documentation,
and
> it has the nice effect of suppressing annoying warnings from "pub publish". 
So
> I think I'll go ahead and leave the dependencies in place.

what about listing these as "any"? That way we don't have to update the
dev_dependencies that often.