On Mar 8, 9:45 am, slabbe <sla...@gmail.com> wrote: > Maybe we could fix an objective for each release instead of just > having the objective of 90% for sage-5.0. Is gaining 1% per release > too much?
I think that any fixed objective for the overall coverage is too much for "the next release." If sage-5.0 aims for 90%, then release managers just will not make such a release until 90% are reached and we will continue having 4.x.y. But if the next release must get 1% and it gets only 0.3% what should the release manager do? Just wait until enough patches will be merged to bump the coverage enough? That does not sound like a good idea. Ask others to write doctests? Who will actually do it and which ones? I think it is very good that 100% coverage is required for the new code, and it is easy to enforce, but who is going to document sage/structure/parent_old.pyx (currently covered at 5%) if this file is eventually going to be deprecated? I am not saying that there is no point in improving doctest coverage, I just think that as with other good possible improvements it is unlikely that there will be enough effort in this direction and it is not good if it becomes an obstacle for other areas that do get done, such as new releases... Thank you, Andrey -- 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
