How to use 'git' effectively while testing rubyripper?

[GoogleCodeExporter]

The version info of rr should update along with the commits.  This would
make bug reporting easier (just look at the gui window instead of checking
with svn or git).  This would also make things easier if somebody has
multiple copies of rr sitting around (who, me?).  In addition it would keep
the chronology which git seems to neglect.  Major commits / changes could
change rr from 0.5.3 to 0.5.4 while minor commits could change it to 0.5.3a
or something.  Might also give a better target of when to release new
official versions.

Original issue reported on code.google.com by mordbr...@gmail.com on 1 Sep 2008 at 10:45

[GoogleCodeExporter]

nah, "a", "b", etc. in the most of cases (>97%) means "alpha", "beta", etc. So 
I'd
recommend to use "0.major.minor.revision", after 1.0 release: 
"major.minor.revision".

Original comment by enql...@vaygr.net on 3 Sep 2008 at 10:03

[GoogleCodeExporter]

You're right, of course.  I don't really care, just so long as there is a way of
telling what version is being used without a meaningless hash being used.

Original comment by mordbr...@gmail.com on 3 Sep 2008 at 10:29

[GoogleCodeExporter]

commits are just there for anyone that wishes to follow the action closely (and 
test
it of course ;) ). But I will not promote it to be a release-like process. It 
would
cost too much of my precious development time.

Better start learning git. Each commit has a parent defined and each commit is
identified by a hash. Besides the hash there is also a timestamp added to each
commit. You can change between commits within a single directory using 
branches(!).
Use gitk to visualize the thing graphically (needs tk/tcl).

I propose to focus our efforts to expand the current [Git] wiki page. It should 
list
some commands which may be usefull for tracking and testing rubyripper.

Please use this issue to put forward the questions you've got about using git. 
Feel
free to help each other as well. I'm in no way an expert. So please consider 
reading
a manual for example before consulting me.

Original comment by rubyripp...@gmail.com on 4 Sep 2008 at 9:32

• Changed title: How to use 'git' effectively while testing rubyripper?
• Changed state: Accepted
• Added labels: Type-Task
• Removed labels: Type-Defect

[GoogleCodeExporter]

Haven't had time to delve into git further, but the timestamp (unwieldy as it is
compare to a version or release number) is better than nothing.

Original comment by mordbr...@gmail.com on 14 Sep 2008 at 5:11

[GoogleCodeExporter]

I thought some discussion would start here. But apparently there was no need 
for such
a thing. Closing the issue.

Original comment by rubyripp...@gmail.com on 13 Jan 2009 at 11:38

• Changed state: Fixed