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

Document Zold::Upgrades #343 #353

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Document Zold::Upgrades #343 #353

wants to merge 3 commits into from

Conversation

botanicus
Copy link
Contributor

This is the Zold::Upgrades documentation requested by @ledestin in #343.

@0crat 0crat added the scope label Jul 6, 2018
@0crat
Copy link
Collaborator

0crat commented Jul 6, 2018

Job #353 is now in scope, role is REV

@0crat
Copy link
Collaborator

0crat commented Jul 6, 2018

This pull request #353 is assigned to @ledestin/z, here is why; the budget is 15 minutes, see §4; please, read §27 and when you decide to accept the changes, inform @yegor256/z (the architect) right in this ticket; if you decide that this PR should not be accepted ever, also inform the architect; this blog post will help you understand what is expected from a code reviewer; there will be a monetary reward for this job

@@ -2,6 +2,22 @@

module Zold
# Class to manage data upgrades (when zold itself upgrades).
#
# This class will write the version file to the zoldata directory.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@botanicus what happened to the draft? This text doesn't explain the case of missing version file.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ledestin added.

@ledestin
Copy link
Contributor

ledestin commented Jul 6, 2018

@botanicus thanks, please see my comment

@codecov-io
Copy link

codecov-io commented Jul 6, 2018

Codecov Report

Merging #353 into master will increase coverage by 0.31%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #353      +/-   ##
==========================================
+ Coverage   33.44%   33.76%   +0.31%     
==========================================
  Files          54       50       -4     
  Lines        2470     2343     -127     
==========================================
- Hits          826      791      -35     
+ Misses       1644     1552      -92
Impacted Files Coverage Δ
lib/zold/node/front.rb 38.12% <0%> (-0.63%) ⬇️
lib/zold/commands/node.rb 21.71% <0%> (-0.51%) ⬇️
lib/zold/wallet.rb 41.57% <0%> (-0.37%) ⬇️
lib/zold/score.rb 49.31% <0%> (-0.02%) ⬇️
lib/zold/commands/push.rb 28.33% <0%> (ø) ⬆️
lib/zold/atomic_file.rb 35.71% <0%> (ø) ⬆️
lib/zold/commands/diff.rb 37.5% <0%> (ø) ⬆️
lib/zold/commands/propagate.rb 29.54% <0%> (ø) ⬆️
lib/zold/json_page.rb 45.45% <0%> (ø) ⬆️
lib/zold/remotes.rb 27.27% <0%> (ø) ⬆️
... and 43 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d659e66...d718899. Read the comment docs.

@botanicus
Copy link
Contributor Author

@ledestin added. Is it good now?

# `upgrades/` have to run. They are named `<version>.rb`, so for
# instance `upgrades/0.0.1.rb` etc.
#
# Only the scripts from the data version up need to run.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@botanicus greater than the data version? Or >=?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're on 0.1 and want to migrate to 0.2, we should run 0.2.rb, 0.1.rb run already when we upgraded to 0.1, I'd say. So I think this is correct.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@botanicus I have a hard time understanding it, and one of my mates too. Could you please change it in the docs?

@ledestin
Copy link
Contributor

ledestin commented Jul 9, 2018

@botanicus thanks, but one more question

@0crat
Copy link
Collaborator

0crat commented Jul 11, 2018

@ledestin/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

@ledestin
Copy link
Contributor

@botanicus what happened? you didn't reply to my last comment.

@botanicus
Copy link
Contributor Author

@ledestin sorry, I'm traveling and didn't have time. Let me rephrase it.

@botanicus
Copy link
Contributor Author

@ledestin I just changed that.

# up to date.
#
# If the data version is lower than Zold::VERSION, we will look into
# the `upgrades/` directory and any scripts from the data version
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@botanicus please don't use data version up, it's ambiguous at least to me. You can also ask @yegor256 to resolve our conflict.

@ledestin
Copy link
Contributor

@botanicus unfortunately, not the change I requested

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

Successfully merging this pull request may close these issues.

4 participants