Release 1.1 (Windows and Version Solver)

[stubailo]

This issue tracks the release of Meteor 1.1. Have any concerns? Mention them here. Finding that the RCs are working great? Mention that here. We will keep this top-level description updated with known issues.

The current RC is 1.1-rc.0. Update an app to the release candidate with:

meteor update --release 1.1-rc.0

For Windows, get the installer here.

The two major additions in this release are:

1. Support for the Windows operating system
2. The new faster and more accurate package version solver

Read the release notes for a complete list of the changes in this release.

TODO before final release

• Sign Windows installer with extended validation certificate
• Email binary package authors to publish their packages for Windows

RC History

• 1.1-rc.0: initial release candidate

[grigio]

Hi, I received this automated message for grigio:babel but I don't depend on native libs anymore, so it works already on any supported arch.

[glasser]

@grigio Yes, I believe this just means that older versions need to be published if you care to allow the older versions to work on Windows (which may or may not make sense based on your package)!

[ghost]

Can you put #3957 (Fix for meteor --test timing issues) into the 1.1 release, please. It's a serious issue for people with bigger apps.

[stubailo]

@sanjo unfortunately, we can't put any more things into 1.1 because we are in the middle of QA and don't want to start over. I'm sure there will be another release soon after with this fix.

[avital]

I don't think we need to restart QA if we take #3957, since it only changes meteor run --test and meteor test-packages --velocity, both of which aren't tested by our QA process.

So I suggest we consider taking the change for 1.1, since I've definitely heard that timing issues are a huge problem for Velocity users. (I assume this change fixes the root problem, but I don't actually know that for a fact.)

[ghost]

I don't think we need to restart QA if we take #3957, since it only changes meteor run --test and meteor test-packages --velocity, both of which aren't tested by our QA process.

So I suggest we consider taking the change for 1.1, since I've definitely heard that timing issues are a huge problem for Velocity users. (I assume this change fixes the root problem, but I don't actually know that for a fact.)

Exactly that. Without the fix meteor run --test and meteor test-packages --velocity will never exit when the testing mirror takes too long to start. This makes using this commands in CI unreliable. Many users have reported this (see linked GitHub issues in pull-request to name a few). The scope of the changes is only the Velocity specific code in Meteor Core, so there should be no risk in putting it still in like Avital said. I've tested the changes manually to make sure they work.

[stubailo]

@sanjo your commit is going to be in 1.1! Awesome.

[ghost]

@stubailo Great! Thanks.

[stubailo]

Released!

[avital]

🎆

[ghost]

@stubailo #3957 seems to not be in 1.1 :-(

[glasser]

@sanjo That appears to be accurate.

[stubailo]

:( I must have made a git error somewhere, my apologies. My intention was
to include it.
On Wed, Apr 1, 2015 at 1:26 AM Jonas Aschenbrenner notifications@github.com
wrote:

@stubailo https://github.com/stubailo #3957
#3957 seems to not be in 1.1 :-(

—
Reply to this email directly or view it on GitHub
#4028 (comment).