Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: docs@httpd.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: Rich Bowen <rbowen@rcbowen.com>
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_DFFAA39A-C311-4F65-8F12-2F1A9BD4B2CB"
Subject: Re: Questions for further discussion about Documentation commentary
 system
Date: Wed, 9 May 2012 09:44:34 -0400
In-Reply-To: <07AB601C-8DBE-41BF-B37C-AC0B79951876@medecine.uhp-nancy.fr>
To: docs@httpd.apache.org
References: <90E76ABC-29E3-4AB1-9213-755051C218EA@medecine.uhp-nancy.fr>
 <4FAA5DF9.4060902@cord.dk>
 <07AB601C-8DBE-41BF-B37C-AC0B79951876@medecine.uhp-nancy.fr>
Message-Id: <CDC58D14-A8E0-4597-BDE5-4A324C9A0E93@rcbowen.com>

--Apple-Mail=_DFFAA39A-C311-4F65-8F12-2F1A9BD4B2CB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On May 9, 2012, at 9:39 AM, Lucien Gentis wrote:

> I agree.
> I only meant that if a comment is 2.2 and 2.4 related, it should =
appear in each version.
> But how could it be achieved ?
> Each time a moderator validates a comment in 2.4 docs for example, he =
should verify
> if it's also 2.2 related, and if it is, port it to 2.2
> This could lead to big work for the moderators.


Sure, but that's what we do now already. When we apply a doc change, we =
have to consider what branches need the change, and make it there, =
otherwise the branches drift out of sync, creating more work later.

--
Rich Bowen
rbowen@rcbowen.com :: @rbowen
rbowen@apache.org


--Apple-Mail=_DFFAA39A-C311-4F65-8F12-2F1A9BD4B2CB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On May 9, 2012, at 9:39 AM, Lucien Gentis =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>I =
agree.</div><div>I only meant that if a comment is 2.2 and 2.4 related, =
it should appear in each version.</div><div>But how could it be achieved =
?</div><div>Each time a moderator validates a comment in 2.4 docs for =
example, he should verify</div><div>if it's also 2.2 related, and if it =
is, port it to 2.2</div><div>This could lead to big work for the =
moderators.</div></span></blockquote></div><div><br></div><div>Sure, but =
that's what we do now already. When we apply a doc change, we have to =
consider what branches need the change, and make it there, otherwise the =
branches drift out of sync, creating more work later.</div><br><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Inconsolata; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Inconsolata; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">--<br>Rich Bowen<br><a =
href=3D"mailto:rbowen@rcbowen.com">rbowen@rcbowen.com</a> :: =
@rbowen<br><a =
href=3D"mailto:rbowen@apache.org">rbowen@apache.org</a><br><br><br><br><br=
><br></div></span></span>
</div>
<br></body></html>=

--Apple-Mail=_DFFAA39A-C311-4F65-8F12-2F1A9BD4B2CB--