search

ecologylab / BigSemanticsWrapperRepository

Repository of wrappers used by the BigSemantics project.
Apache License 2.0
3 stars 9 forks source link

Repository version number should be placed with wrappers. #1

Closed quyin closed 9 years ago

quyin commented 11 years ago

So that programs in multiple platforms can use it.

Service should also use this too.

Modification time stamp / hash might be a better choice than a pure version number. A git commit number can possibly be used.

andru1d commented 11 years ago

which of those versioning schemes do you advocate?

andruid

On Thu, Jan 31, 2013 at 7:52 PM, quyin notifications@github.com wrote:

So that programs in multiple platforms can use it.

Service should also use this too.

Modification time stamp / hash might be a better choice than a pure version number. A git commit number can possibly be used.

— Reply to this email directly or view it on GitHubhttps://github.com/ecologylab/bigSemanticsWrapperRepository/issues/1.

andruid kerne, ph.d. director, interface ecology lab associate professor, department of computer science and engineering texas a&m university 979.862.3684 fax college station, tx 77843-3112 http://ecologylab.net

http://facebook.com/ecologylab

Interfaces are the multidimensional border zones through which the interdependent relationships of people, activities, codes, components, and systems are constituted. Interface ecology investigates the dynamic interactions of media, cultures, and disciplines that flow through interfaces.

quyin commented 11 years ago

at this point of time I'm inclined to a date based version number (e.g. 13.02 means the version released on Feb 2013) plus a hash code calculated using the whole wrapper repository.

I like date based version numbers because it is very clear. this number can be used to determine which version is newer.

the hash code can be used to determine if two versions have the same contents, for example, web/mobile clients may use this to refresh the locally cached version.

both can be generated by the compiler and placed somewhere in the wrapper repository itself.

andru1d commented 11 years ago

sounds good to me!

andruid

On Thu, Jan 31, 2013 at 10:56 PM, quyin notifications@github.com wrote:

at this point of time I'm inclined to a date based version number (e.g. 13.02 means the version released on Feb 2013) plus a hash code calculated using the whole wrapper repository.

I like date based version numbers because it is very clear. this number can be used to determine which version is newer.

the hash code can be used to determine if two versions have the same contents, for example, web/mobile clients may use this to refresh the locally cached version.

both can be generated by the compiler and placed somewhere in the wrapper repository itself.

— Reply to this email directly or view it on GitHubhttps://github.com/ecologylab/bigSemanticsWrapperRepository/issues/1#issuecomment-12971070.

andruid kerne, ph.d. director, interface ecology lab associate professor, department of computer science and engineering texas a&m university 979.862.3684 fax college station, tx 77843-3112 http://ecologylab.net

http://facebook.com/ecologylab

Interfaces are the multidimensional border zones through which the interdependent relationships of people, activities, codes, components, and systems are constituted. Interface ecology investigates the dynamic interactions of media, cultures, and disciplines that flow through interfaces.

rhema commented 11 years ago

That's a nice and clean way to do it.

ghost commented 11 years ago

:+1: I like this. I'll probably adopt the date released scheme for versioning in the future w/ simpl de/serialization

quyin commented 9 years ago

A single sequential version number causes potential issues with conflicts. It seems to me that the overall version number for the whole repository should be maintained through releasing / tagging, and for individual wrappers we now have hashes to know if it is stale.