Robert Bradshaw wrote:
> On Apr 23, 2009, at 11:21 AM, Dag Sverre Seljebotn wrote:
> 
>> Dag Sverre Seljebotn wrote:
>>> I added a "Documentation" milestone and component. Rushing ahead  
>>> to do
>>> other useful stuff instead of staying behind perfecting documentation
>>> can't be helped IMO, but filing a ticket is much easier to do and  
>>> such a
>>> list is probably very useful.
>>>
>>> I could even much easier add the actual documentation text as I go  
>>> to a
>>> ticket, which has much lower startup overhead than editing the
>>> documentation itself.
>>>
>>> Let me know if I'm wrong and should remove it again :-)
> 
> No, that's a very good idea.
> 
>> Also I propose that every such ticket has a "Since" field in the
>> description field. E.g. for packed structs I stated our next release.
>>
>> http://trac.cython.org/cython_trac/ticket/294
> 
> Isn't this redundant with the milestone field?

I'm sure it can be discussed, but that's an emphatic "no" from me.

Milestones are mainly for scheduling -- scheduling work and scheduling 
branches. If I assigned a doc ticket to 0.11.2, I think that's the same 
as saying "we want to see if we can get this documented before we 
release 0.11.2". Which is silly at this stage. (But e.g. in Sage you'd 
easily do something like that, i.e. "we want documentation to have this 
quality before releasing". Like the doctests goals.)

What I want with the "Since" field is to have that more or less 
literally end up in the documentation.

Example: I could create a new doc ticket now for something in buffers 
which I remembered, assign it to milestone 0.12 because I'd really like 
to get it done by the 0.12 release, but have a "Since" field of 0.10 
since the feature happened to be available by then.

You *do* have the "Version" trac field, which we don't use. Using a 
comment just seemed simpler.

BTW I prefer my trac tickets served by report 3

http://trac.cython.org/cython_trac/report/3

This may be less important in other reports.

-- 
Dag Sverre
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev

Reply via email to