all pages should be tagged accordingly even if they need to just be
updated. One great example would be the community help wiki of ubuntu. I am
not saying create a pdf. Once a page is obsolete it should be tagged as so.
saying this page is obsolete and the version its meant for is no longer
supported.
As well I think a good rule of thumb would be to tag the pages that apply
to what versions.
On Tue, May 20, 2014 at 6:27 PM, Vesa <dii....@nbl.fi> wrote:
> On 05/20/2014 07:09 PM, musikbear wrote:
> > Imo a lot in the current pages are still valid, and 'just' need 'some'
> > ajustments. + new imagery! -i have already thrown my 10 cent there,
> buuut a
> > good thing should be repeated :p :Central ImageDB!
> >
> >
>
> You can already upload images directly on the wiki... what else do you
> need?
>
>
>
> ------------------------------------------------------------------------------
> "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
> LMMS-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lmms-devel
>
--
Jonathan Aquilina
------------------------------------------------------------------------------
"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
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
