|
From: Steve S. <ste...@mu...> - 2018-04-04 08:59:40
|
On Mon, Apr 2, 2018 at 6:19 PM Gabriele Pohl <gp...@di...> wrote: > at the time when ssm and me worked together filling the Munin Guide > with content from the wiki, we three agreed on the following: > > The Munin Guide build from repo master > will present info for _all_ Munin versions > as we don't have enough time to maintain multiple > versions of the Guide. > Indeed. Having a stable-2.0 branch would be the best, as it is what other projects to successfully, but we do not have the manpower to operate it. And that's the most important fact now. > Now I see that content concerning the stable 2.0 version > has been removed from the master Munin Guide. > Oops, that's a mistake. Note that TheMuninGuide still shows the various versions (latest & stable-2.0). I'll fix that to remove the stable-2.0 branch to make it clear. > To give the people a clear understanding > we should introduce markers in typographic > or logo style to mark/outline which information > is valid for which version. Fully aligned on that. If there is a 2.0 or "3.0" specific it should be written clearly, like a sort of #ifdef in the doc. Th > @Quentin: Are you willing to create such logos for the Munin Guide? > We might use the munin white background logo for 2.0 features, and the green one for 3.0 only features. We'd just need a smaller version of those to make it nicer, but a scale down could do for now. > @Steve and all who are familiar with version 2.999: > I would be happy if you review it and add version markers accordingly ~ > Will do. -- Steve |