Hi, guys, Sorry to jump occasionally in this thread. Here I want to mention a few things: 1. this is not required for home:xxx, right? just for devel and factory. 2. version scheme should be comparable with releases eg: Indeed, 1.0.0.git20130910 is smaller than 1.0.0 (osc seems can do this check) But we can't bump the version to 1.0.1right because it's not released. Meantime in a human-being's eyes, 1.0.0.git20130910 is bigger than 1.0.0 2. "+" mostly of times means "combination" So 1.0.0+git20130910, how can a release be combined with a git version? It's just weird, confusing a lot of people...although it's a solid workaround for the bigger/smaller math thing. 3. hashes is not a good idea. hashes are important, but only to those who actually check out from git/svn and know how to check. And most of the upstream projects has a web GUI, but hashes are always the last line of a table. It is just because it's useless to most of the people. People who decide to check out always want a latest version, he don't even care about the hashes unless some upstream developer tells him to check a specific version. So hashes are only convenient for us in the list. But version number is shown to everyone. Users must have a clear idea of what state this software has been at. They don't even know which hash is greater than what. Even zypper/osc don't know yet. In short, it's useless to users. I think git20130910 might be good idea. you know it's from git, you know it's state, if you wanna search, github has a timestamp (although some heavy contributors may commit many times a day, but actually it's not a good habit) To us, sometimes we have to compromise for something if it's good for most of the people. Anyway we can run a diff in such rare case. Anyway date is very very important, we can add hashes but we can't skip it. Greetings Marguerite -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org