And that would have to be solved anyway, not just for REST API.
I guess each major version branch should have its own documentation tree.
Anyway +1 to keeping only one REST API doc and avoiding duplication.
m.
On 06/29/2011 02:46 PM, Galder Zamarreño wrote:
I believe confluence can deal with different versions of the same
document (I vaguely remember this from a conversion w/ Mark N but can't find an email
ref)
Besides, maintaining documents in Confluence is easier than manually editing HTML
On Jun 29, 2011, at 2:35 PM, Emmanuel Bernard wrote:
> How do you cope with version change. The nicety with embedded doc is that it's
the one for the software version you use.
>
> On 29 juin 2011, at 14:22, Galder Zamarreño<galder(a)redhat.com> wrote:
>
>> The REST server comes with a small web app containing an HTML with the
documentation in
https://docs.jboss.org/author/display/ISPN/Accessing+data+in+Infinispan+v...
>>
>> Keeping the documentation in both places is a waster of energy and it can quickly
get out of sync.
>>
>> I proposed the HTML gets changed to point to
https://docs.jboss.org/author/display/ISPN/Accessing+data+in+Infinispan+v...
and keep the docu up to date there.
>>
>> Thoughts?
>> --
>> Galder Zamarreño
>> Sr. Software Engineer
>> Infinispan, JBoss Cache
>>
>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Michal Linhard
Quality Assurance Engineer
Red Hat Czech s.r.o.
Purkynova 99 612 45 Brno, Czech Republic
phone: +420 532 294 320 ext. 62320
mobile: +420 728 626 363