That's a good point. Maybe we could come up with a documentation download that does just package up a section of the wiki.
-Mike On Fri, 2005-03-04 at 21:14 +0000, sebb wrote: > If the docs are only on the Wiki, then the built-in JMeter help will > stop working, surely? > > I think we need to provide documentation with the JMeter download, so > JMeter can be used on systems that don't have Internet access. > > If the Wiki documentation can be easily packaged up and included in > JMeter downloads, then perhaps it would be OK, but I'm not sure that > would be easy. Wiki markup is not HTML... > > S. > On Fri, 4 Mar 2005 15:32:01 -0500, Peter Lin <[EMAIL PROTECTED]> wrote: > > I like the idea of letting the users edit the docs, since often it's > > too much hassle for users to checkout the docs, make a patch, submit > > patch and then we commit it. > > > > peter > > > > > > On Fri, 04 Mar 2005 15:20:34 -0500, Michael Stover <[EMAIL PROTECTED]> > > wrote: > > > On Fri, 2005-03-04 at 20:10 +0000, sebb wrote: > > > > OK by me, with one proviso - would it be easy to optionally generate > > > > JMX files in the old format? That should make the transition easier > > > > for some. > > > > > > Yeah, I can do that. > > > > > > > > > > > I am intending to create a 2.0.3 release soon, as there are quite a > > > > few useful fixes in 2.0. > > > > > > > > S. > > > > On Fri, 4 Mar 2005 11:47:03 -0500, Peter Lin <[EMAIL PROTECTED]> wrote: > > > > > I'll try to move the webservice related docs on wiki this weekend > > > > > also. along with general clean up. > > > > > > > > > > peter > > > > > > > > > > > > > > > On Fri, 04 Mar 2005 11:08:02 -0500, Mike Stover <[EMAIL PROTECTED]> > > > > > wrote: > > > > > > I plan on devoting some of my time in the next 2 weeks to > > > > > > 1. cleaning out obsolete documentation in the wiki > > > > > > 2. Moving the User Manual from the web site to the wiki > > > > > > > > Not sure about this at all - why would that help? > > > > > > Because we have a lot of trouble keeping the docs up-to-date, and a lot > > > of useful user information is split between the user-manual and the wiki > > > area. If we put it all on the wiki, users can update the documenation > > > for us (ie, users often learn things about the components I don't even > > > know/realize - no reason they can't put it in the documentation directly > > > if it's on the wiki). > > > > > > Plus, updating the docs becomes easier - just change the wiki, forget > > > about writing it in xml then transforming it to html then uploading to > > > apache... > > > > > > > > > > > > > 3. Putting finishing touches on the code in CVS HEAD > > > > > > 4. Making the 2.1 branch in preparation for a release. > > > > > > > > > > > > What do people think? > > > > > > > > > > > > -Mike > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
