Rahul Akolkar wrote:
> First, thanks for putting this together. Its great to have the docs updated.
>
> While I have not looked at the document in detail, some high-level
> comments below ...
>
> On Mon, Apr 5, 2010 at 11:23 AM, Phil Steitz wrote:
>> I have made my first attempt at updating the
On Wed, Apr 7, 2010 at 11:52 AM, sebb wrote:
> On 07/04/2010, Rahul Akolkar wrote:
>> On Tue, Apr 6, 2010 at 1:37 AM, Henri Yandell wrote:
>>
>>
>> >
>> > I've been deleting desirable goals from the docs :)
>> >
>> > I think it's more desirable that they be short, sweet and focused;
>> > t
On 07/04/2010, Rahul Akolkar wrote:
> On Tue, Apr 6, 2010 at 1:37 AM, Henri Yandell wrote:
>
>
> >
> > I've been deleting desirable goals from the docs :)
> >
> > I think it's more desirable that they be short, sweet and focused;
> > than that they cover all possibilities.
> >
>
>
>
> Id
On Tue, Apr 6, 2010 at 1:37 AM, Henri Yandell wrote:
>
> I've been deleting desirable goals from the docs :)
>
> I think it's more desirable that they be short, sweet and focused;
> than that they cover all possibilities.
>
Ideally:
* half a screen-full's worth recipe on one webpage, no scroll
First, thanks for putting this together. Its great to have the docs updated.
While I have not looked at the document in detail, some high-level
comments below ...
On Mon, Apr 5, 2010 at 11:23 AM, Phil Steitz wrote:
> I have made my first attempt at updating the documentation here:
> http://commo
erify it from Europe, the
> proxy IP 209.237.227.195 does not work. (Ping fails, telnet 209.237.227.195
> 80 fails). Any updated IP ?
> Thanks
I've been using:
minotaur-2.apache.org:80 = 140.211.11.10:80
from the UK.
>
> --
> View this message in context:
> http://
ork. (Ping fails, telnet 209.237.227.195
80 fails). Any updated IP ?
Thanks
--
View this message in context:
http://n4.nabble.com/all-Release-preparation-documentation-tp1751669p1753162.html
Sent from the Commons - Dev mailing list archive at
On Mon, Apr 5, 2010 at 1:54 PM, sebb wrote:
> I think it might be useful to add a note regarding consistency between
> changes.xml, RELEASE-NOTES and JIRA.
>
> For example, if JIRA FOO-1234 is fixed in release 1.2, then IMO it
> should have a JIRA "fix" release of 1.2, and appear in the
> changes
On 05/04/2010, Phil Steitz wrote:
> I have made my first attempt at updating the documentation here:
> http://commons.apache.org/releases/index.html
>
> Given that the previous docs were so out of date as to be pretty
> much worthless, I thought it best to push things along with CTR -
> actual
Luc Maisonobe wrote:
> Phil Steitz a écrit :
>> I have made my first attempt at updating the documentation here:
>> http://commons.apache.org/releases/index.html
>
> Thanks for this documentation, Phil.
>
> I have one question and one comment.
>
> In the "Create the release candidate" section, y
Phil Steitz a écrit :
> I have made my first attempt at updating the documentation here:
> http://commons.apache.org/releases/index.html
Thanks for this documentation, Phil.
I have one question and one comment.
In the "Create the release candidate" section, you write: "Note that the
release cand
I have made my first attempt at updating the documentation here:
http://commons.apache.org/releases/index.html
Given that the previous docs were so out of date as to be pretty
much worthless, I thought it best to push things along with CTR -
actually "PTR" (p = publish). I am sure there are some
12 matches
Mail list logo