On 05/ 5/11 04:47 PM, kcrisman 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.
I like SPKG.txt. Personally I would have called the file "ChangeLog" in common
with just about every other software project, but SPKG.txt does. I think that
summerises the changes much better than what "hg log" does, where often there
are numerous changes made when a ticket gets reviewed.
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?
- kcrisman
Automatic generation would be more accurate and more detailed. I don't feel
however it would be better. I suspect it will have a lot of details that one
does not see (or want), when trying to get a quick overview of what has happened
to a package.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
--
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
