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.

Sign up for GitHub

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

Jump to bottom

The master branch will reflect InfluxDB 2.0 development on Friday, January 11, 2019 #10618

Closed
mark-rushakoff opened this issue Jan 9, 2019 · 6 comments
Closed

The master branch will reflect InfluxDB 2.0 development on Friday, January 11, 2019 #10618

mark-rushakoff opened this issue Jan 9, 2019 · 6 comments
Labels
wontfix

Comments

@mark-rushakoff
Copy link
Contributor

Please refer to Paul's blog post: https://www.influxdata.com/blog/influxdb-master-branch-to-switch-to-2-0-on-jan-11/

This Friday, the code on master will be moved to a new 1.8 branch, and master will reflect the full history of 2.0 development which currently lives at https://github.com/influxdata/platform. As noted in https://github.com/influxdata/platform/issues/2358, the platform repository will be archived.

The influxdb repository will remain the correct place to file issues or pull requests against 1.x versions of InfluxDB.

The existing history of the influxdb project will not be affected. Any references to existing SHAs or tags will continue to work. However, if you depend on the master branch, that dependency will break this Friday.
@mark-rushakoff mark-rushakoff pinned this issue Jan 9, 2019
@mark-rushakoff
Copy link
Contributor Author

I'm starting to transfer in some issues from the platform repository now.

@mark-rushakoff
Copy link
Contributor Author

The platform repository has been archived. Development will continue on influxdb's next branch until this Friday, at which point we will merge the next branch into the master branch.

@mark-rushakoff
Copy link
Contributor Author

At approximately 2019-01-10T19:00:00Z (about 24 hours after this post), we'll create a 1.8 branch from master, and then we'll merge the content of the next branch over master and delete the next branch.

@mark-rushakoff
Copy link
Contributor Author

Branch switch is happening now, and then I'm going to retarget all open PRs as necessary.

@mark-rushakoff
Copy link
Contributor Author

The branch switch is finalized:

  • master now reflects 2.0 development
  • What used to be on master is now on the 1.8 branch
  • The next branch has been deleted
  • All outstanding PRs have been retargeted to the appropriate base branch

Thanks everyone for helping to make this a smooth transition.

@mark-rushakoff mark-rushakoff unpinned this issue Jan 11, 2019
mark-rushakoff referenced this issue Jan 11, 2019
@mark-rushakoff
Wipe out workspace in preparation for v2 merge
f2898d1 
"Knock knock."

"Who's there?"

"InfluxDB Veet."

...
Arista-Jenkins pushed a commit to aristanetworks/goarista that referenced this issue Jan 11, 2019
@7AC
influxlib: switch to aristanetworks fork
e064134 
The fork is pinned at v1.6.5 which is the last release before
influxdata/influxdb@f2898d1.
The commit is part of the larger effort in
influxdata/influxdb#10618 which makes a
breaking change.

We can't handle this with Go modules because of
golang/protobuf#751, which in turn depends on
golang/go#24250 which will be fixed with
go1.12.

Change-Id: I43b643fcab202d94bd529dfce135fb4e3f5add52
@stale
Copy link

stale bot commented Jul 23, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mark-rushakoff