I hope I asked this question sometime back and no one answered. Anyway,
here we go.
Deepal Jayasinghe wrote:
Hi all;
In the xdoc folder contains document for already released versions (0.93
, 0.94) and current version. And I dont think we need to keep multiple
doc folders inside xdocs for
I hope I asked this question sometime back and no one answered. Anyway,
here we go.
Deepal Jayasinghe wrote:
Hi all;
In the xdoc folder contains document for already released versions (0.93
, 0.94) and current version. And I dont think we need to keep multiple
doc folders inside xdocs for
Hi,
I think we can make a better decision if we are clear about Apache
policy about maintaining docs for older revisions [Before a 1.0
version and after]. So can some one jump in an enlighten us on what
is the policy for dealing with old docs.
Best Regards,
Chamil Thanthrimudalige
On
Hi all,
Yes I agree that the person who does it should have a major part in
deciding 'how' to do it (and ofcourse Chatra is doing a great job -
no doubts about it) But if that person chooses a particularly complex
and not-very-appropriate solution I think we, as a community should be
pointing
On Tue, 2006-03-21 at 14:33 +0600, Chamil Thanthrimudalige wrote:
Hi,
I think we can make a better decision if we are clear about Apache
policy about maintaining docs for older revisions [Before a 1.0
version and after]. So can some one jump in an enlighten us on what
is the policy
h , I do not want to start a war :)
Eran Chinthaka wrote:
I hope I asked this question sometime back and no one answered.
Anyway, here we go.
Deepal Jayasinghe wrote:
Hi all;
In the xdoc folder contains document for already released versions (0.93
, 0.94) and current version. And I
Ok, time to compromise ;-)
Lets maintain two versions of the documents inside the xdocs. One with
the *released* version of docs and the other with *latest *version of
the docs.
And lets have all the versions of the documents in the site. *BUT, *we
will update only the documents of the
+1 from me to maintain 'released' and 'latest' versions of documents
in the SVN head.
Thanks,
Ruchith
On 3/21/06, Eran Chinthaka [EMAIL PROTECTED] wrote:
Ok, time to compromise ;-)
Lets maintain two versions of the documents inside the xdocs. One with
the *released* version of docs and the
+1 :)
Eran Chinthaka wrote:
Ok, time to compromise ;-)
Lets maintain two versions of the documents inside the xdocs. One with
the *released* version of docs and the other with *latest *version of
the docs.
And lets have all the versions of the documents in the site. *BUT, *we
will
Cool :) +1.
Damn, I was going to enjoy giving boxing gloves to see open source
developers fight about documentation!!!
Sanjiva.
On Tue, 2006-03-21 at 16:25 +0600, Eran Chinthaka wrote:
Ok, time to compromise ;-)
Lets maintain two versions of the documents inside the xdocs. One with
:-)
Well 2 versions seems to be an ok middle ground. +1 from me too.
Chamil
On Mar 21, 2006, at 5:27 PM, Sanjiva Weerawarana wrote:
Cool :) +1.
Damn, I was going to enjoy giving boxing gloves to see open source
developers fight about documentation!!!
Sanjiva.
On Tue, 2006-03-21 at
Damn, I was going to enjoy giving boxing gloves to see open source
developers fight about documentation!!!
Or a soccer ball, since the world cup is approaching. ;-) +1 to a good compromise.
Robert
http://www.braziloutsource.com/ On 3/21/06, Sanjiva Weerawarana
[EMAIL PROTECTED]
Hi all,
Ok I'm also +1 to the compromise but I have a small issue to be clarified.
Once a release is out we do a SVN tag (and I've been told that tags
automatically become branches, of which I'm not really sure about - If
not lets say we always start a branch after a tag which seems to be
the
I hope we can apply our builder extensions theory here, but
unfortunately for the same person :-D
(for those who doesn't know what this builder extensions theory is,
please search for the mails of Axis2 during its start up days)
-- Chinthaka
Ajith Ranabahu wrote:
Hi all,
Ok I'm also +1 to
Or a soccer ball, since the world cup is approaching.
yapee.u got a die hard soccer fan here.
yes+1 for compromise. on a more prcatical aspect pl do understand you cannot freeze documentation like you freeze code.
chatraOn 3/21/06, robert lazarski [EMAIL PROTECTED] wrote:
Damn, I was
ok,
I guess I went overboard with my theory of strictly maintaining the
current docs in SVN (That's no reason to pull out that old builder
extension thing anyway :( ) but I guess I'm more biased to doing
things the right way rather than the easy way (which is unfortunately
not the same and
hey ajith,
you did hear my reply...may be not on mail. but i did +1 chinthaka's solution.
anyways for the record here goes:
one thing i have to make clear is that once a release has been made and
the code frozen it is very impractical to think that you can freeze the
documentaion with it.
17 matches
Mail list logo
