How to track the version of the corresponding source material? about discovermeteor_ja HOT 6 CLOSED

There's already the version number but you're right, maybe the commit source would be helpful as well.

But would this be per-file? Or just on the changelog?

from discovermeteor_ja.

I was thinking of doing this on a per-file basis, but I hadn't realized the book is already versioned. So then, it'd be simpler to:

1. Create a tag for each version on the English repository
2. Agree on a target version of the book to translate and note it somewhere
   • on the changelog, readme and/or GitHub milestones?
3. Always work from the corresponding tag of the source repo

from discovermeteor_ja.

Sounds good, just tagged the last update:

https://github.com/DiscoverMeteor/DiscoverMeteor_En/releases/tag/1.7

When you say "Agree on a target version of the book to translate", I assume this would be per language? If so yeah I think GitHub milestones would work.

The only problem is what happens if we release version 1.8 while you're working on 1.7? Should people keep working on 1.7, or switch to 1.8 right away?

from discovermeteor_ja.

Great!
Yes, "target version" would be per language.

The only problem is what happens if we release version 1.8 while you're working on 1.7?

Hmm, I guess it depends on the changes between the versions.

If it's a major overhaul and we can expect people to want to read the previous version in a coherent state from head to tail, then it makes sense to finish 1.7 first and move on to the next version.

If not, then I'd say it's better to base off from the latest version when starting a new chapter, to save the hassle of diffing and applying the changes. If someone is in the middle of translating a chapter, it'd be up to them to choose when to switch to the latest version.

Considering these cases, we might want to track the versions on a per-file basis after all.

from discovermeteor_ja.

I think the best way is to just try out a method and see what happens. We're kind of letting each translation project organize as they want, so as long as everybody in the repo agrees feel free to establish a new rule :)

from discovermeteor_ja.

@SachaG Alrighty =)

Superseded by #11

from discovermeteor_ja.