First time here? Check out the FAQ!

Ask Your Question
2

Checklist for submitting a patch to trac

asked 10 years ago

this post is marked as community wiki

This post is a wiki. Anyone with karma >750 is welcome to improve it.

I would like to create a checklist that one should go through before submitting a patch to the trac server:

What are the points to be checked before submitting a patch to the trac server?

Preview: (hide)

1 Answer

Sort by » oldest newest most voted
0

answered 10 years ago

this post is marked as community wiki

This post is a wiki. Anyone with karma >750 is welcome to improve it.

This answer is community wiki; please add your points here (please provide commands/links on how to do this)

  1. run doctests (sage -t filename.py)
  2. build and check documentation (sage -docbuild all html)
  3. add your name to list of authors
Preview: (hide)
link

Comments

I'd run doctests for all files unless it is very clear it only touches a certain file/directory. Probably running long doctests isn't a bad idea too, though that is more annoying with the patchbots apparently not working.

kcrisman gravatar imagekcrisman ( 10 years ago )

Similarly, documentation only needs to be checked if there is something that changed in doc...

kcrisman gravatar imagekcrisman ( 10 years ago )
2

On the other hand, I have been bitten by failing doctests inside RST files that could only be tested by 'make ptestlong', so that's what is the best answer. Let me add to the list item #0: write a doctest for every computation path that you change/add.

rws gravatar imagerws ( 10 years ago )

I would also suggesting building the pdf manual too. I have been bitten by this quite a few times.

KnS gravatar imageKnS ( 10 years ago )

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 10 years ago

Seen: 776 times

Last updated: Aug 20 '14