[Bf-docboard] Documenting Features for Future Release

[Francesco Siddi]

Hi,
Sphinx supports versioning, and I think we could simply push updates to the docs until a release is available (ideally features should be documented as they are developed). Once the release is out, we update the documentation tag to the following release number and keep updating the docs.

This way older tags will always be available (and built) and we would have a bleeding edge version of the docs as well.

Before release would be nice to agree on this! Let’s see what Campbell thinks.

Francesco

On 4 Mar 2015 at 15:48:36, Wayne Campbell (wayneinbc at gmail.com) wrote:

Do we have a procedure for this?   For example I have claimed the task to document 'Viewport depth-of-field and Screen-space-ao'.  I believe this is an upcoming 2.74 feature.  Is there a way to update the docs, but defer publishing the update until 2.74 is released?  

I suppose we are close enough to the 2.74 release that it doesn't matter in this case, but generally we need a procedure that allows documenting these features as they are added, without the updated information becoming visible until the feature is released.


Wayne
_______________________________________________  
Bf-docboard mailing list  
Bf-docboard at blender.org  
http://lists.blender.org/mailman/listinfo/bf-docboard  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-docboard/attachments/20150304/a2d33cc0/attachment.htm