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

What do releases mean? #2339

Closed
dhalperi opened this issue Feb 2, 2021 · 6 comments
Closed

What do releases mean? #2339

dhalperi opened this issue Feb 2, 2021 · 6 comments
Labels
topic: meta / release Meta issues around plugin release process type: question

Comments

@dhalperi
Copy link

dhalperi commented Feb 2, 2021

Today, as often, I got a notification that there was a new release on this repo. (v2021.02.02).

When I look at the Bazel IntelliJ plugin versions page, I see this most recent release:

  • Bazel plugin version 2021.01.29.1.1
  • Date of release: Feb 01, 2021
  • What's new:
    v2021.01.19
    
    ===========
    
    * Bug fixes and internal cleanup.
    

note that v2021.01.19 is the previous release.

It would be nice to be able to line up the different versions. Is this documented somewhere / can you explain what they mean?

The thing that seems most true, possibly, is that that the IntelliJ plugin is released ~1-2 days before the next GitHub release (Bazel plugin released yesterday, GitHub release today), but claims to be for the prior release.

  • Is this mislabeling, or accurate?
  • If accurate, is the intent to let releases "bake" in GitHub before releasing them in IntelliJ repo? Who is using the github release tags vs from the IntelliJ distribution?

Anything as a user I can do to help with the release process or beta-test early versions?

@jvolkman
Copy link

jvolkman commented Feb 2, 2021

I'm not familiar with the exact release process for this plugin, but I do know that there is a Jetbrains-mandated review period for new versions in their repo. Releases aren't listed there immediately, unlike Github.

@mai93 mai93 added type: question topic: meta / release Meta issues around plugin release process labels Feb 5, 2021
@AlexeyGy
Copy link
Collaborator

@jvolkman is correct, we like to release early here so people who want to build the plugin themselves can have early access to bugfixes and features.
The changelog has the aforementioned default message if we don't have any noteworthy new features (we don't intend to include every commit in the changelog).

@dhalperi
Copy link
Author

@AlexeyGy - The current pattern I've seen is that every single time there's a new release in IntelliJ, the next day there's a new GitHub release. This has held up at least since I filed this issue, in maybe 3 releases.

IIUC, you're saying that the IntelliJ release is always for the prior GitHub release? And this is desired -- as opposed to, say, the IntelliJ release being a few days after the GitHub release -- independent of the next GitHub release?

@AlexeyGy
Copy link
Collaborator

@dhalperi it's very simple: the JetBrains release is last week's Github release*.

  • unless there are bugs which we may hotfix before uploading to JetBrains. We don't create a new Github release for them but you can get the fixes via git pull.

@dhalperi
Copy link
Author

Okay, nice. Sorry -- the part that I missed is that you are now committed to doing weekly releases? So that the JetBrains release is actually only 7 days after the last release?

(Observationally, the timing of the JetBrains release is tied to subsequent github, not prior github, release).

@AlexeyGy
Copy link
Collaborator

you are now committed to doing weekly releases?
We release every two weeks.

So that the JetBrains release is actually only 7 days after the last release?
approximately

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: meta / release Meta issues around plugin release process type: question
Projects
None yet
Development

No branches or pull requests

4 participants