On 10/25/12 18:52 , Coss, David wrote: > Perhaps this is a another argument for versions on server/api code. > One file to find changes is convenient. I think this makes sense for > a version ChangeLog, which will change *much less* frequently than > SCM revisions/commits, because versions grow slower than commits. > Then you'll have general overview changes in the ChangeLog, which > follows api/server versions and this we reside alongside frequent > commit comments, which go where they belong in the SCM system. Seems > like best of both worlds to me, unless how I phrased it made no > sense... (possible :-D )
It does make sense :-) However, such a changelog would be generated by git log and/or git shortlog. Furthermore it might not be tracked itself (avoid redudancy), it could just be put onto a web server, alongside the release archive. Oliver _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
