Git repo / release schedule
Cantor, Scott
cantor.2 at osu.edu
Fri Jan 19 13:15:55 UTC 2024
> Could you maybe briefly describe what the process should be to submit
>these changes? Just create a diff and send it to you/some e-mail or
> create a merge request?
I wouldn't have bothered with the repository if you don't want to interact with it directly (which is to say, I can still just delete it).
My intention was that people would ask for commit access and get me their public key to get access to commit to it.
Basically there are 2 options here:
- Use it directly, which means getting public keys in place to access them.
- Don't bother with it and just use Jira, which requires Atlassian accounts and access to Jira.
> Also, when you wrote in your email from Dec. 5th "we will definitely
> diff these files when we start getting close to any releases": What did
> you mean by that? Will there be a diff somewhere showing what has to be
> translated?
No, I'm saying whatever people commit to the repository will be pulled into the releases when it's time to do them. Diffing would be a sanity check, but really we're just going to copy over those files (other than the English ones, which I'm keeping In sync the other direction).
-- Scott
More information about the i18n
mailing list