Re: [ros-dev] ReactOS Repository migrated to GitHub

[Can Tasan]

Congrats for switching into Github! Just a little question.

Is there any way to return using revision numbers? Current hash-based commit tagging might
be confusing, hard to find, not reflecting at-the-time state of development since we have
relied on SVN for a long time. Also for bug reporting, revision numbers is more helpful.

Secondly, for example, Wine don't (and probably won't) care for hashes as everyone
out there uses release builds, and release period is just 2 weeks. That's not the case
for ReactOS. In just a few commits big changes might occur, and everyone retests. 3
months? Avalanche!

If it isn't viable, could we seek for another solution? (e.g timestamp...)

Lastly, git.reactos.org is quite simple for watching the stream, and perfect!

Best regards,
Can

[Alexander Sh.]

We gonna use git-describe. It starts counting from the last tag – 0.4.7-dev and also
includes commit hash. See https://git-scm.com/docs/git-describe

От: Can Tasan
Отправлено: среда, 4 октября 2017 г. в 21:53
Кому: 'ReactOS Development List'
Тема: Re: [ros-dev] ReactOS Repository migrated to GitHub

Congrats for switching into Github! Just a little question. 

Is there any way to return using revision numbers? Current hash-based commit tagging might
be confusing, hard to find, not reflecting at-the-time state of development since we have
relied on SVN for a long time. Also for bug reporting, revision numbers is more helpful.

Secondly, for example, Wine don't (and probably won't) care for hashes as everyone
out there uses release builds, and release period is just 2 weeks. That's not the case
for ReactOS. In just a few commits big changes might occur, and everyone retests. 3
months? Avalanche!

If it isn't viable, could we seek for another solution? (e.g timestamp...)

Lastly, git.reactos.org is quite simple for watching the stream, and perfect!

Best regards,
Can