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

missing commits/fixes in 1.8.4 #20685

Open
cbonte opened this issue Feb 3, 2021 · 5 comments
Open

missing commits/fixes in 1.8.4 #20685

cbonte opened this issue Feb 3, 2021 · 5 comments

Comments

@cbonte
Copy link
Contributor

cbonte commented Feb 3, 2021

The 1.8.4 version has just been released but some commits/patches have disappeared between 1.8.4-rc3 and 1.8.4-rc4.
A new 1.8.4 branch was created https://github.com/influxdata/influxdb/tree/1.8.4
whereas some fixes were provided in a 1.8 branch till 1.8.4-rc3 : https://github.com/influxdata/influxdb/tree/1.8

Also, the release note claims the 1.8.3 version was not released, which is not the case :
https://github.com/influxdata/influxdb/releases/tag/v1.8.4
https://www.influxdata.com/blog/release-announcement-influxdb-oss-2-0-3/

What happened to this 1.8.4 release ?

@superbool
Copy link

Also confused with "the 1.8.3 version was not released",but the tag v1.8.3 who build it?

And which is the main branch of 1.x now?
It seems that master-1.x is behind of 1.8.4

Just very confused.🤔️

@cbonte
Copy link
Contributor Author

cbonte commented Feb 14, 2021

Hi @davidby-influx, do you have any details about this ? Thanks.

@psteinbachs
Copy link
Contributor

Apologies for the confusion on this, but I will attempt to clarify. The changelog note in 1.8.4 was intended for 1.8.3 Enterprise only which we need to correct, but we did indeed tag and release 1.8.3 OSS. We did not release 1.8.3 Enterprise due to a regression that could reduce write performance in some cases.

Between 1.8.3 and 1.8.4, we produced several RC builds that rolled back changes as part of identifying the regression (hence why the commits disappeared). With 1.8.4 out now, any commits that did not make it in are being re-evaluated for the 1.8.5 release. master-1.x appearing to be behind 1.8.4 is odd because that shouldn't be the case (we're looking into it further), and master-1.x is always meant to be the main branch for 1.x

@cbonte
Copy link
Contributor Author

cbonte commented Mar 2, 2021

Hi @psteinbachs, this is still embarrassing because nothing has been done yet to cleanup the branches, but new commits are added to master-1.x. From the outside, it's really hard to understand any logic here.

@dgnorton
Copy link
Contributor

dgnorton commented Mar 2, 2021

@cbonte

...nothing has been done yet to cleanup the branches, but new commits are added to master-1.x...

Work is in progress to cleanup the 1.8.x issues. In parallel, there is new feature work happening on master-1.x.

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

No branches or pull requests

5 participants