On 5/5/11 3:29 PM, Jeroen Demeyer wrote:
On 2011-05-05 20:20, Dr. David Kirkby wrote:
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 agree with David on this, but maybe that is partially because I'm not
very fluent with hg. My personal spkg workflow is NOT to commit changes
until at the very last moment, such that "hg diff" always gives the diff
against the last version. So I modeled the merger script to make this
workflow easier (by not having to do the last step of committing the
changes).
I guess this suits my workflow too--I would just make extra commits in
between versions. So for me:
1. make all the changes, committing as I go like I would normally do.
2. Make an entry in SPKG.txt which summarizes these changes, as sort of
a changelog for the version bump.
3. Upload the spkg so that Jeroen's script makes one more commit which,
in effect, tags the version number and commits a summary changelog in
SPKG.txt.
That sounds perfect! The details will still be in the hg log from my
commits as I go, and a high-level summary is in the SPKG.txt and
committed as one last commit to the repository.
Jason
--
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
