Early GitLab CE/EE release candidate

To test/deploy the new metrics on GitLab.com we'll need to prepare a new RC for GitLab CE/EE (as I'd like to properly test this before the 22nd). Due to the metrics being a pretty big feature (and one that may cause instability) a patch release would not suffice. I've been testing the system on dev.gitlab.org but this uses only a single server, opposed to the 50-something servers used for GitLab.com.

@rspeicher: what can I do to make this process as easy as possible?

cc @sytses

mentioned in issue #4071 (closed)

I was looking at the schedule the other day and thinking the same thing - RC1 isn't slated to be deployed until the 18th, which doesn't leave a lot of time for real-world testing.

Maybe we can build and deploy RC1 on the 14th. What do you think, @JobV?

Milestone changed to 8.4

I probably sound like a douche, but is there a possibility to do it before the 14th? Based on past experiences I highly doubt I'll need only a single deploy to tame this beast, so every extra day would be a win. If not the 14th is also fine, but anything after that and I fear I won't be able to test things properly before the 22nd.

I guess that's dependent on the state of omnibus and our willingness to basically deploy master onto GitLab.com

cc @jacobvosmaer @marin

It probably depends on merging CE master into EE as well, which looks like it hasn't been done in a while. cc @vsizov

@yorickpeterse I'm sure @vsizov is busy with Elasticsearch, so if you'd handle the EE merge that would probably help speed things up. :)

@rspeicher, @yorickpeterse yes, it would be cool. /cc @dzaporozhets

There were lots of holidays so I don't think it should be too complex.

I guess that's dependent on the state of omnibus

Omnibus-gitlab master needs a bit more testing on my side but I should be done today/tomorrow(12/13.01.2016). Whether we want GitLab EE master on GitLab.com is a question for @jacobvosmaer or @jnijhof

I do not have a clear picture of what is going on in CE master, or EE master, or how the two might bite each other once merged. But I am always up for live-editing code in production during office hours.

I created a merge request (CE -> EE master) a week ago https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/107 it was waiting for fix from @Kamil and @grzesiek. But know everything is OK and someone should continue my work on that MR.

I'm with you @rspeicher. Build and deploy as early as possible and iterate as often as possible.

EE master is ready for an RC1 tag - let's go for it.

I'll leave it to @jacobvosmaer @marin @yorickpeterse to handle in the CET morning. Needs tagging, packaging, deploying.

Three people were mentioned meaning no one will end up doing it.

@marin consider doing in a hangout with @yorickpeterse

@sytses Thanks, I intend on doing so after I finish some things I started on already(that involve other team members).

@yorickpeterse Created a MR to sync EE and CE master again https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/113 . The build is on dev https://dev.gitlab.org/gitlab/gitlab-ee/commit/5c32336fbb6dbd80e96238cc360e2c62a767dae5/builds . Once green I will merge to master and run the release tool. After that its the regular rc1 release schedule which I will follow up on. Depending on time when everything is ready we can have rc1 deployed tonight or better, tommorow.

EE and CE packages are being built.

Rc1 was deployed on GitLab.com

Thanks @marin @jnijhof

Status changed to closed

Thanks!

mentioned in merge request !14785