stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nirmal Fernando <nirmal070...@gmail.com>
Subject Re: [Discuss] [Wiki] Maintaining Verisions in Apache Stratos (incubating) Wiki
Date Wed, 04 Dec 2013 03:31:01 GMT
Oh... you can't always ask people to switch to the latest version :)
Impractical IMO.


On Wed, Dec 4, 2013 at 8:06 AM, Isuru Perera <isurup@wso2.com> wrote:

> Do we really need to maintain docs for previous versions? Since we will be
> releasing versions in short durations, I don't think it's a good idea to
> restructure wiki like this. We will also be recommending to use latest
> version. We can have the significant info for each version in same pages.
>
> This is just my personal opinion.
>
>
> On Tue, Dec 3, 2013 at 3:30 AM, Mariangela Hills <mariangela@wso2.com>wrote:
>
>> The wiki is powered by Confluence. In Confluence each page name needs to
>> be unique. Therefore, we can not have two pages with the same name.
>>
>> How about we use one of the following structures for the manuals. The
>> following structures are based on a hypothetical scenario, taking into
>> account that we have released 4.0.0 and we are working on the docs of a new
>> release (e.g., 5.0.0) which has not been released yet.
>> (1)
>> - Documentation
>>     - 4.0.0-incubating
>>         - 4.0.0 Getting Started
>>         - 4.0.0 User Guide
>>         - 4.0.0 Developer Guide
>>         - 4.0.0 Testing Procedure
>>     - 3.0.0-incubating
>>         - 3.0.0 Getting Started
>>         - 3.0.0 User Guide
>>         - 3.0.0 Developer Guide
>>         - 3.0.0 Testing Procedure
>>   - Future Release
>>     - 5.0.0-incubating
>>         - 5.0.0 Getting Started
>>         - 5.0.0 User Guide
>>         - 5.0.0 Developer Guide
>>         - 5.0.0 Testing Procedure
>>
>> (2)
>> - Documentation
>>   - 4.0.0-incubating
>>         - 4.0.0 Getting Started
>>         - 4.0.0 User Guide
>>         - 4.0.0 Developer Guide
>>         - 4.0.0 Testing Procedure
>>  - Archives
>>     - 3.0.0-incubating
>>         - 3.0.0 Getting Started
>>         - 3.0.0 User Guide
>>         - 3.0.0 Developer Guide
>>         - 3.0.0 Testing Procedure
>>  - Future Release
>>     - 5.0.0-incubating
>>         - 5.0.0 Getting Started
>>         - 5.0.0 User Guide
>>         - 5.0.0 Developer Guide
>>         - 5.0.0 Testing Procedure
>>
>> Please let me know which structure is more suitable or whether you have a
>> better idea.
>> I vote for 2
>>
>> Regards,
>> Mariangela
>>
>>
>>
>> *--Mariangela Hills*
>> Senior Technical Writer
>> Mobile:(+94)773500185
>>
>> WSO2 Inc. http://wso2.com/
>>
>>
>> On Mon, Dec 2, 2013 at 10:59 AM, Imesh Gunaratne <imesh@apache.org>wrote:
>>
>>> I think we could create a new Root Node called "Documentation" and move
>>> "Getting Started", "User Guide", "Developer Guide", "Testing Procedure" to
>>> each version. WDYT?
>>>
>>> Sample:
>>>
>>> - Documentation
>>>     - 3.0.0-incubating
>>>         - Getting Started
>>>         - User Guide
>>>         - Developer Guide
>>>         - Testing Procedure
>>>     - 4.0.0-incubating
>>>         - Getting Started
>>>         - User Guide
>>>         - Developer Guide
>>>         - Testing Procedure
>>>
>>>
>>> Appreciate your feedback.
>>>
>>> Thanks
>>> Imesh
>>>
>>>
>>>
>>> On Sat, Nov 30, 2013 at 8:34 AM, Imesh Gunaratne <imesh@apache.org>wrote:
>>>
>>>> Hi All,
>>>>
>>>> Currently Apache Stratos (incubating) Wiki navigation structure looks
>>>> like below:
>>>>
>>>> [image: Inline image 3]
>>>>
>>>> May be we could improve it by grouping the versions under a element
>>>> called "Documentation". Something similar to Axis2 Wiki:
>>>>
>>>> [image: Inline image 4]
>>>>
>>>> What do you think?
>>>>
>>>> Thanks
>>>> Imesh
>>>>
>>>
>>>
>>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>



-- 
Best Regards,
Nirmal

Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.

Blog: http://nirmalfdo.blogspot.com/

Mime
View raw message