On Thu, May 5, 2011 at 8:47 AM, kcrisman <kcris...@gmail.com> wrote: > >> > Further ideas, suggestions, complaints are welcome. >> >> I agree with the sentiment expressed elsewhere in previous threads that >> the changelog should be in the hg log, and not necessarily in the >> SPKG.txt file. In other words, I feel like the changes you made should >> be reversed---the hg log messages should be insisted on, and the >> changelog inside the SPKG.txt should be generated from the hg log. But >> it doesn't matter enough to me to change what you've done. > > I think having the SPKG.txt is a very nice way for someone to get a > quick overview of this. For instance, they could be attached to the > main Sage page so that people can see how we've been changing/updating > to upstream. hg logs would be different. But as Jason says, this has > been hashed elsewhere.
WIth no resolution, so thanks for suggesting a solution. > I do agree that getting SPKG.txt to be automatically generated from > changelogs would be a nice way to get better changelogs, so maybe I am > agreeing with Jason? +1, I find it more natural to work with hg. To support both workflows, another option is to support going both ways--if there are uncommitted changes, make an hg entry based on the spkg.txt, otherwise, update spkg.txt based on the changelog entry + spkg filename. - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
