On 05/15/2014 11:21 PM, Stian Jørgensrud wrote:
> I have decided not to make special pages for 1.0 instruments. So 0.4
> instruments on the wiki will change, however most (all?) of the instruments
> have just added functionality, so the guide still applies for 0.4. This also
> means links will be broken and wrong in the 0.4 manual, but as the pages
> follow the same structure as 1.0 for now people could easily search and find
> those pages anyway. Alternatively someone can make a page, actually generate
> a page which lists all 0.4 pages.
>
Personally I don't think there's much value in dividing the wiki in
sections for each version iteration.
Reason is simple: right now it's just 0.4 manual and upgrading it to a
1.0 manual. But what happens when 1.1 comes in next month - will we then
go through the same hassle of creating a whole new 1.1 manual? What
about when 1.2 comes in september? Or 1.3 at the end of the year... how
many manuals do we need?
It'd be better to just scrap all these "versioned manuals" and just have
one user manual. Within the pages there can be subsections for
functionality of different /supported versions... /0.4 is no longer
supported and it shouldn't even be a consideration in these discussions.
Images should IMO be taken from the newest version always.
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel