Hmm, seems everyone is agreeing. So who opposed this earlier? :D

Chatra Nakkawita wrote:
+1 from me too. Like you said....I agree that any changes of a previous release should be made in the branch itself.

And yes, this is not the first time we've had this arguement :-)

Chatra

On 9/29/06, *Afkham Azeez* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    I fully agree with Deepal. Maintaining two versions of the
    documentation on the trunk is an adhoc way of version management.
    When SVN does such a good job, why should we go for such an adhoc
    structure? We never do this for the code, so why special treatment
    for the docs? As Deepal said, the correct way of doing this should
    be cutting a branch in SVN after the 1.1 release, and any
    documentation bugs in 1.1 should be fixed in that branch (and most
    probably, also in the trunk). BTW, I think this is not the first
    time this has been argued on this list :D

    Azeez


    On 9/29/06, *Deepal Jayasinghe* <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:

        Hi Chatra and all,

        Well , I know we had the same kind of structure for previous
        releases as
        well . But I am -1 on keeping two doc folders.  And I can not
        name any
        other Apache project which use this kind of document structure.
        In the
        meantime keeping duplication data make unnecessary  complication ,
          - if we find error in one document ,  need to change them in two
        location. Is that good habit (I dont think so)
          - If some one new to Axis2 , and if he download Axis2 what
        kind of doc
        structure will he get ? if I download Axis2 today do I need to know
        about the previous version docs. (I know its useful to have them
        in the
        web site , but not in the code base)

        And remember , we use "SVN" and after each release we cut a
        branch , so if
        some one want to update old doc , go and update them in the
        branch (if you
        think it is really necessary, o.w just update that in the
        current SVN)

        Specially I dont like to have version related stuff , in the
        current code
        base , if we have we should remove them.

        Finally , this is the first time I -1 in this mailing list ,
        that is b'coz
        I honestly dont like that  :).

        Thanks
        Deepal



        Chatra Nakkawita wrote:
        >  Hi,
        >
        >  Just a note to let you know that the latest dir in the
        >
        https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/
        <https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/>
        is
        >  now renamed as 1_1.
        >
        >  This was done as part of updating/creating documents for
        upcoming Axis2
        >  1.1 release and to  make sure that all the links in terms of
        Axis2 1.1
        >  documents work. The documents for this release are been worked on
        >  currently. Any document updates in terms of Axis2 1.1 version
        needs to
        >  be made on
        >
        https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/1_1
        
<https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/1_1>.
        >
        >  Once Axis2 1.1 is released, we will create a latest dir (which
        will
        >  start off as a copy of the final 1_1 dir, to make sure that we
        use an
        >  up-to-date documents version) which will serve as the working
        document
        >  directory. Which means that after 1.1 release what ever
        updates in terms
        >  of the worked on Axis2 version will be made on the new
        'latest' dir.
        >
        >  Thanks & regards,
        >
        >  Chatra
        >
        >
        >
        ---------------------------------------------------------------------
        >  To unsubscribe, e-mail: [EMAIL PROTECTED]
        <mailto:[EMAIL PROTECTED]>
        >  For additional commands, e-mail: [EMAIL PROTECTED]
        <mailto:[EMAIL PROTECTED]>



        ---------------------------------------------------------------------

        To unsubscribe, e-mail: [EMAIL PROTECTED]
        <mailto:[EMAIL PROTECTED]>
        For additional commands, e-mail: [EMAIL PROTECTED]
        <mailto:[EMAIL PROTECTED]>




-- Thanks Afkham Azeez



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to