Thanks for the info. I did the changes in trunk and thought they would stay long enough in the sites svn to be replaced by the next release process.
Felix Am 29. Juli 2017 12:57:24 MESZ schrieb sebb <[email protected]>: >On 25 July 2017 at 10:50, Milamber <[email protected]> wrote: >> Felix, >> >> It's not the good way to change the JMeter website. Your changes will >be >> erased in the next update of website using the right way. > >Yes and no. > >It's fine to make changes in trunk if the change does not need to be >propagated to the current version of the site. > >> You must make the changes on > >I think that should be: > >"You must also make the changes on" > >It's important that trunk is updated otherwise the changes will be >lost from the next version. > >> jmeter/branches/docs-3.2/docs/ >> >> And after copy the changes to /jmeter/site/ from the docs-3.2 branch >using >> svnmucc utility. >> >> See : https://wiki.apache.org/jmeter/ReleaseCreation section "Publish >JMeter >> site" >> >> Milamber >> >> >> >> >> On 24/07/2017 17:42, [email protected] wrote: >>> >>> Author: fschumacher >>> Date: Mon Jul 24 16:42:12 2017 >>> New Revision: 1802844 >>> >>> URL: http://svn.apache.org/viewvc?rev=1802844&view=rev >>> Log: >>> Remove wrong css-tag >>> >>> Modified: >>> jmeter/site/css/new-style.css >>> >>> Modified: jmeter/site/css/new-style.css >>> URL: >>> >http://svn.apache.org/viewvc/jmeter/site/css/new-style.css?rev=1802844&r1=1802843&r2=1802844&view=diff >>> >>> >============================================================================== >>> --- jmeter/site/css/new-style.css (original) >>> +++ jmeter/site/css/new-style.css Mon Jul 24 16:42:12 2017 >>> @@ -391,7 +391,6 @@ table { >>> .section-index { >>> font-family: "Merriweather"; >>> - margin:; >>> list-style: none; >>> } >>> >>> >>> >>
