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

"Freeze" all old runs #419

Open
hroncok opened this Issue Jun 5, 2018 · 6 comments

Comments

Projects
None yet
2 participants
@hroncok
Member

hroncok commented Jun 5, 2018

In order to make new changes safe, I porpose we freeze all runs by serving them from another branch.

My idea is to:

  1. create archived2017 branch and put all runs from 2017 in there
  2. create archived2018 branch and put all past runs from 2017 in there
  3. make the maintainers (@encukou, @vahalova?) to use forks for the current runs (for pyladies, preferably fork to @PyLadiesCZ, I cannot do that)

Alternative would be to use separate forks for each run, but I don't think it's worth the effort.

I can proceed with 1 and 2.

@hroncok hroncok added the forks label Jun 5, 2018

@encukou

This comment has been minimized.

Member

encukou commented Jun 6, 2018

The current run in Brno will end in a month, so we can add it to the archived2018 branch then, instead.

@hroncok

This comment has been minimized.

Member

hroncok commented Jun 6, 2018

Sure. If no changes are required.

@hroncok

This comment has been minimized.

Member

hroncok commented Jun 7, 2018

Can I proceed with 1 and 2?

@encukou

This comment has been minimized.

Member

encukou commented Jun 7, 2018

Go ahead, please.
If the freezing API needs to change, we can touch the archived branches then.

@hroncok

This comment has been minimized.

Member

hroncok commented Jun 7, 2018

2017: #420

@hroncok

This comment has been minimized.

Member

hroncok commented Jul 1, 2018

Let's wait 10+ days and archive 2018 at once.

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