Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release - September 2018 - name: 0.18.0 #5963

Closed
laurentlb opened this issue Aug 22, 2018 · 76 comments
Closed

Release - September 2018 - name: 0.18.0 #5963

laurentlb opened this issue Aug 22, 2018 · 76 comments
Assignees
Labels

Comments

@laurentlb
Copy link
Contributor

@aehlig Can you take care of the release 0.18.0?

@aehlig
Copy link
Contributor

aehlig commented Aug 23, 2018 via email

@laurentlb
Copy link
Contributor Author

Sounds good, we can target September 10 or 11.

@hlopko
Copy link
Member

hlopko commented Sep 3, 2018

It's actually awesome, because I can finish my incompatible flags cls :)))

@laszlocsomor
Copy link
Contributor

laszlocsomor commented Sep 3, 2018

Potential blocker: #6061
(Need to verify if 0.18.* is affected or whether the bug is a regression.)

Update(2018-09-10): verified that this is not a blocker.

@aehlig
Copy link
Contributor

aehlig commented Sep 10, 2018 via email

@laszlocsomor
Copy link
Contributor

laszlocsomor commented Sep 10, 2018

@aehlig : Yes, that commit is beyond ddc97ed so #6061 is not a blocker. Thanks for checking!

@laszlocsomor
Copy link
Contributor

Another potential blocker: #6099
I'll test the RC to see if it's affected.

@aehlig
Copy link
Contributor

aehlig commented Sep 10, 2018 via email

@laurentlb
Copy link
Contributor Author

Some cherrypicks of 0.17 are not included in your baseline.

@hlopko
Copy link
Member

hlopko commented Sep 10, 2018

Please consider picking a later baseline, since we decided to follow https://docs.bazel.build/versions/master/skylark/backward-compatibility.html quite late, we rushed to submit needed cls:

@scentini to verify I didn't miss anything

@aehlig
Copy link
Contributor

aehlig commented Sep 10, 2018 via email

@aehlig
Copy link
Contributor

aehlig commented Sep 10, 2018 via email

@lberki
Copy link
Contributor

lberki commented Sep 10, 2018

/cc @cushon

@cushon
Copy link
Contributor

cushon commented Sep 10, 2018

@lberki are you planning to include 7eb9ea1 in 0.18 too?

@cushon
Copy link
Contributor

cushon commented Sep 10, 2018

@aehlig can you cherry-pick c6eef5d for #6105?

@lberki
Copy link
Contributor

lberki commented Sep 11, 2018

@mhlopko is informing me that there will be a new baseline

@aehlig
Copy link
Contributor

aehlig commented Sep 11, 2018

Will also check if tomorrow's nighly is suitable as a base line.

Looks good. The only thing we have to look at is what's going on with Gerrit and jdk9 as this might be bazel related.

So, let's push the baseline forward to c062b1f instead of starting with too many cherry-picks right from the beginning.

@hlopko
Copy link
Member

hlopko commented Sep 11, 2018

Fantastic, thanks Klaus!

@davido
Copy link
Contributor

davido commented Sep 11, 2018

The only thing we have to look at is what's going on with Gerrit and jdk9 as this might be bazel related.

Can you share the logs?

@aehlig
Copy link
Contributor

aehlig commented Sep 11, 2018 via email

@aehlig
Copy link
Contributor

aehlig commented Sep 11, 2018

rc2 is available at https://releases.bazel.build/0.18.0/rc2/index.html

Please test!

@davido
Copy link
Contributor

davido commented Sep 11, 2018

@aehlig Thanks, I see that @meteorcloudy already created extra issue for this breakage.

@aehlig
Copy link
Contributor

aehlig commented Sep 11, 2018

Thanks, I see that @meteorcloudy already created extra issue for this breakage.

This is #6127.

@lberki
Copy link
Contributor

lberki commented Sep 11, 2018

...aand, the first cherrypick request: 2834613 to fix #6060 (a regression between 0.16 and 0.16.1, still in 0.17)

@dslomov
Copy link
Contributor

dslomov commented Oct 5, 2018

rc9 is created using

scripts/release/release.sh create --force_rc=9 0.18.0 c062b1f 2834613 2579b79 faaff7f b073a18 bf6a63d c1a7b4c 71926bc 86a8217

It is available on https://releases.bazel.build/0.18.0/rc9/index.html

@petemounce
Copy link
Contributor

rc-4-9 pushed to chocolatey.

@sdqali
Copy link

sdqali commented Oct 10, 2018

Thank you for taking on this release. When can we expect this to be out?

@aehlig
Copy link
Contributor

aehlig commented Oct 10, 2018 via email

@hlopko
Copy link
Member

hlopko commented Oct 15, 2018

I'm not sure what the process is, so just to be sure I'll say that I'll perform an incompatible change flip (#6380) in 0.19, so 0.18 should probably mention it as an incoming incompatible change. Or not, if we're not yet doing the new process.

@laurentlb
Copy link
Contributor Author

laurentlb commented Oct 15, 2018

To suggest changes to the announcement, see: https://docs.google.com/document/d/1wDvulLlj4NAlPZamdlEVFORks3YXJonCjyuQMUQEmB0/edit

@hlopko
Copy link
Member

hlopko commented Oct 15, 2018

That sounds like something I should have done instead spamming this thread :) Thanks Laurent :)

@aehlig
Copy link
Contributor

aehlig commented Oct 15, 2018

As there are no new blockers, releasing now.

@aehlig
Copy link
Contributor

aehlig commented Oct 15, 2018

https://github.com/bazelbuild/bazel/releases/tag/0.18.0

@aehlig aehlig closed this as completed Oct 15, 2018
@petemounce
Copy link
Contributor

Pushed to chocolatey.

@laurentlb
Copy link
Contributor Author

I think we need a patch release 0.18.1 to fix #6292.

@meteorcloudy
Copy link
Member

We need to cherry-pick 914b4ce for #6292

@aehlig
Copy link
Contributor

aehlig commented Oct 22, 2018 via email

@meteorcloudy
Copy link
Member

@aehlig Thanks for dealing with this.

Can you just make sure

      if (ccToolchain(ruleContext).supportsInterfaceSharedObjects()) {
        ccLinkingHelper.emitInterfaceSharedObjects(true);
      }

is added after CcLinkingHelper ccLinkingHelper = initializeLinkingHelper(featureConfiguration, deps);
in CcProtoAspect.java?

@aehlig
Copy link
Contributor

aehlig commented Oct 23, 2018 via email

@aehlig
Copy link
Contributor

aehlig commented Oct 24, 2018 via email

@aehlig
Copy link
Contributor

aehlig commented Oct 24, 2018 via email

@meteorcloudy
Copy link
Member

I think the non-JDK issue is already fixed in 0.19.0 or at least from HEAD.
See this issue #6214

@meteorcloudy
Copy link
Member

Due to some CI change, we cannot test 0.18.0rc3 on our CI. But I ran a test on my local Windows machine that confirmed the manually cherry-pick did fix #6292.

@petemounce
Copy link
Contributor

0.18.1 rc3 pushed to chocolatey. Please could a new release issue be opened for new releases? It's quite easy to miss, otherwise; this ticket is closed.

@ittaiz
Copy link
Member

ittaiz commented Oct 26, 2018

Can you please cherry pick e025726 for #6456? Thanks! Cc @cushon

@aehlig
Copy link
Contributor

aehlig commented Oct 29, 2018 via email

@ittaiz
Copy link
Member

ittaiz commented Oct 29, 2018 via email

@petemounce
Copy link
Contributor

0.18.1-rc4 is published to chocolatey.

@aehlig
Copy link
Contributor

aehlig commented Oct 31, 2018 via email

@petemounce
Copy link
Contributor

0.18.1 is pushed to chocolatey

@ahippler
Copy link
Contributor

ahippler commented Nov 1, 2018

bazel-0.18.1-installer-darwin-x86_64.sh is missing while the sha and the signature are available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests