Quote:
Originally Posted by JustAMan
No, what I'm saying is, currently we have, say, locale-ru_RU.jar in update-blala-ru_RU-install.bin
I propose having locale-5.0.0-ru_RU.jar, locale-5.0.3-ru_RU.jar, etc. That would bloat a bit the size of updates but it would let us stop worrying about incompatible (i.e. those we'd be unable to backport) changes in the properties.
If you object having different, but compatible, .jars, then we can still use different .jars for incompatible changes, like having locale-5.0.0-5.0.3-ru_RU.jar and locale-5.0.4-5.x.x-ru_RU.jar (this is named pretending 5.0.4 breaks backward compatibility).
|
Yes, this is obvious plan. I think
ixtab came up to the same solution, but he didn't mentioned it because for now there is no need to think about it. There are no incompatible changes at the moment. Single locale-ru_RU.jar built from 5.0.3 resources will serve well for 5.0.0, 5.0.1 and 5.0.3 and it's not the hack solution, this is completely valid. And it will serve well even if incompatible changes will be introduced in 5.0.4 or later.
I'm thinking that what I'm saying is pretty obvious for you. So we're arguing about obvious things
(Though, I can't speak for
ixtab for sure. I can't read his mind
Maybe his point of view is different from what I'm thinking it is. Maybe he will participate in discussion about possible future multiplicity of JARs. But possible future problem with JARs doesn't bothers me. I'm worrying about another aspect.)
What matters for now (for me) is how to place that single changed file at Git repo and Transifex. Should we just replace the same file in 5.0.0 sub-directory with file from 5.0.3 firmware as
ixtab proposed (and I've agreed because it's simple working solution)? Or should we introduce new 5.0.3 sub-directory and place new file there (as I'd like it to be because it provides sensible separation of files from different firmwares)?
Quote:
Originally Posted by JustAMan
I still think we should put different .properties to different Git branches, however that probably implies we'd have to have full copies of source properties there, not only differences (I dunno if it's possible in git to "checkout" in the same folder two branches at the same time).
|
Both branches can contain full set of resources in working copy and there will be no duplication of similar files in repository (i.e. in .git directory).