Question on groovy documentation at http://groovy.codehaus.org/Operators

[Roshan Dawrani-2]

Hi,
A basic doubt on groovy's documentation at http://groovy.codehaus.org/.

Which version of groovy behavior the documentation at http://groovy.codehaus.org/ is supposed to reflect - considering 1.5.x (in stable use), 1.6.x (mid-way) and 1.7.x(nearing a RC release) are all alive simultaneously and they have can have quite different behavior across versions at various places?

rgds,
Roshan

[Guillaume Laforge-2]

Hi Roshan,

Ideally, we would have two different wikis, or different sections for
each version.
But so far, what we've done is indicating that this or that paragraph,
section or feature is about version x or y of Groovy, to indicate the
difference.

Guillaume

On Sat, Nov 7, 2009 at 06:32, Roshan Dawrani <roshandawrani@...> wrote:

> Hi,
> A basic doubt on groovy's documentation at http://groovy.codehaus.org/.
>
> Which version of groovy behavior the documentation at
> http://groovy.codehaus.org/ is supposed to reflect - considering 1.5.x (in
> stable use), 1.6.x (mid-way) and 1.7.x(nearing a RC release) are all alive
> simultaneously and they have can have quite different behavior across
> versions at various places?
>
> rgds,
> Roshan
>

--
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Roshan Dawrani-2]

That arrangement is a bit messy - because at a place where it's not mentioned what version the behavior is for, it is not clear whether it's because the behavior is common across all versions or whether it is just outdated and not updated.

Lots of confusions/questions seem to be coming on the mailing-list because what is documented on the groovy website doesn't work a particular version of groovy and of-course, the documentation doesn't mention the version of groovy at that place.

And when that happens, you don't know how to update the documentation - split one piece of documentation into say 4 - one for each version of groovy? :-)

-- Roshan

On Sat, Nov 7, 2009 at 2:01 PM, Guillaume Laforge <glaforge@...> wrote:

Hi Roshan,

Ideally, we would have two different wikis, or different sections for
each version.
But so far, what we've done is indicating that this or that paragraph,
section or feature is about version x or y of Groovy, to indicate the
difference.

Guillaume

On Sat, Nov 7, 2009 at 06:32, Roshan Dawrani <roshandawrani@...> wrote:
> Hi,
> A basic doubt on groovy's documentation at http://groovy.codehaus.org/.
>
> Which version of groovy behavior the documentation at
> http://groovy.codehaus.org/ is supposed to reflect - considering 1.5.x (in
> stable use), 1.6.x (mid-way) and 1.7.x(nearing a RC release) are all alive
> simultaneously and they have can have quite different behavior across
> versions at various places?
>
> rgds,
> Roshan
>

--
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[Guillaume Laforge-2]

Yes, it's not easy to properly reflect the differences or new features
between version.
The idea is to just note the differences in the documentation as they arise.

On Sat, Nov 7, 2009 at 10:03, Roshan Dawrani <roshandawrani@...> wrote:

> That arrangement is a bit messy - because at a place where it's not
> mentioned what version the behavior is for, it is not clear whether it's
> because the behavior is common across all versions or whether it is just
> outdated and not updated.
>
> Lots of confusions/questions seem to be coming on the mailing-list because
> what is documented on the groovy website doesn't work a particular version
> of groovy and of-course, the documentation doesn't mention the version of
> groovy at that place.
>
> And when that happens, you don't know how to update the documentation -
> split one piece of documentation into say 4 - one for each version of
> groovy? :-)
>
> -- Roshan
>
> On Sat, Nov 7, 2009 at 2:01 PM, Guillaume Laforge <glaforge@...>
> wrote:
>>
>> Hi Roshan,
>>
>> Ideally, we would have two different wikis, or different sections for
>> each version.
>> But so far, what we've done is indicating that this or that paragraph,
>> section or feature is about version x or y of Groovy, to indicate the
>> difference.
>>
>> Guillaume
>>
>> On Sat, Nov 7, 2009 at 06:32, Roshan Dawrani <roshandawrani@...>
>> wrote:
>> > Hi,
>> > A basic doubt on groovy's documentation at http://groovy.codehaus.org/.
>> >
>> > Which version of groovy behavior the documentation at
>> > http://groovy.codehaus.org/ is supposed to reflect - considering 1.5.x
>> > (in
>> > stable use), 1.6.x (mid-way) and 1.7.x(nearing a RC release) are all
>> > alive
>> > simultaneously and they have can have quite different behavior across
>> > versions at various places?
>> >
>> > rgds,
>> > Roshan
>> >
>>
>>
>>
>> --
>> Guillaume Laforge
>> Groovy Project Manager
>> Head of Groovy Development at SpringSource
>> http://www.springsource.com/g2one
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>

--
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Roshan Dawrani-2]

Ok.

Last question on this for now:

Is the way to update the http://groovy.codehaus.org/ documentation to use the wiki at http://docs.codehaus.org/display/GROOVY/ and publish the content? They synch-up immediately? Or, is there any content-change approval step in between?

-- Roshan

On Sat, Nov 7, 2009 at 3:44 PM, Guillaume Laforge <glaforge@...> wrote:

Yes, it's not easy to properly reflect the differences or new features
between version.
The idea is to just note the differences in the documentation as they arise.

On Sat, Nov 7, 2009 at 10:03, Roshan Dawrani <roshandawrani@...> wrote:
> That arrangement is a bit messy - because at a place where it's not
> mentioned what version the behavior is for, it is not clear whether it's
> because the behavior is common across all versions or whether it is just
> outdated and not updated.
>
> Lots of confusions/questions seem to be coming on the mailing-list because
> what is documented on the groovy website doesn't work a particular version
> of groovy and of-course, the documentation doesn't mention the version of
> groovy at that place.
>
> And when that happens, you don't know how to update the documentation -
> split one piece of documentation into say 4 - one for each version of
> groovy? :-)
>
> -- Roshan
>
> On Sat, Nov 7, 2009 at 2:01 PM, Guillaume Laforge <glaforge@...>
> wrote:
>>
>> Hi Roshan,
>>
>> Ideally, we would have two different wikis, or different sections for
>> each version.
>> But so far, what we've done is indicating that this or that paragraph,
>> section or feature is about version x or y of Groovy, to indicate the
>> difference.
>>
>> Guillaume
>>
>> On Sat, Nov 7, 2009 at 06:32, Roshan Dawrani <roshandawrani@...>
>> wrote:
>> > Hi,
>> > A basic doubt on groovy's documentation at http://groovy.codehaus.org/.
>> >
>> > Which version of groovy behavior the documentation at
>> > http://groovy.codehaus.org/ is supposed to reflect - considering 1.5.x
>> > (in
>> > stable use), 1.6.x (mid-way) and 1.7.x(nearing a RC release) are all
>> > alive
>> > simultaneously and they have can have quite different behavior across
>> > versions at various places?
>> >
>> > rgds,
>> > Roshan
>> >
>>
>>
>>
>> --
>> Guillaume Laforge
>> Groovy Project Manager
>> Head of Groovy Development at SpringSource
>> http://www.springsource.com/g2one
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>

--

Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[Guillaume Laforge-2]

The website is a kind of templated layer on top of the Confluence content.
And sometimes, you don't see the changes right away.
If you want to force the appearance of the change, you can append ?nc
to the end of the (website) URL.

On Sat, Nov 7, 2009 at 11:23, Roshan Dawrani <roshandawrani@...> wrote:

> Ok.
>
> Last question on this for now:
>
> Is the way to update the http://groovy.codehaus.org/ documentation to use
> the wiki at http://docs.codehaus.org/display/GROOVY/ and publish the
> content? They synch-up immediately? Or, is there any content-change approval
> step in between?
>
> -- Roshan
>
> On Sat, Nov 7, 2009 at 3:44 PM, Guillaume Laforge <glaforge@...>
> wrote:
>>
>> Yes, it's not easy to properly reflect the differences or new features
>> between version.
>> The idea is to just note the differences in the documentation as they
>> arise.
>>
>> On Sat, Nov 7, 2009 at 10:03, Roshan Dawrani <roshandawrani@...>
>> wrote:
>> > That arrangement is a bit messy - because at a place where it's not
>> > mentioned what version the behavior is for, it is not clear whether it's
>> > because the behavior is common across all versions or whether it is just
>> > outdated and not updated.
>> >
>> > Lots of confusions/questions seem to be coming on the mailing-list
>> > because
>> > what is documented on the groovy website doesn't work a particular
>> > version
>> > of groovy and of-course, the documentation doesn't mention the version
>> > of
>> > groovy at that place.
>> >
>> > And when that happens, you don't know how to update the documentation -
>> > split one piece of documentation into say 4 - one for each version of
>> > groovy? :-)
>> >
>> > -- Roshan
>> >
>> > On Sat, Nov 7, 2009 at 2:01 PM, Guillaume Laforge
>> > <glaforge@...>
>> > wrote:
>> >>
>> >> Hi Roshan,
>> >>
>> >> Ideally, we would have two different wikis, or different sections for
>> >> each version.
>> >> But so far, what we've done is indicating that this or that paragraph,
>> >> section or feature is about version x or y of Groovy, to indicate the
>> >> difference.
>> >>
>> >> Guillaume
>> >>
>> >> On Sat, Nov 7, 2009 at 06:32, Roshan Dawrani
>> >> <roshandawrani@...>
>> >> wrote:
>> >> > Hi,
>> >> > A basic doubt on groovy's documentation at
>> >> > http://groovy.codehaus.org/.
>> >> >
>> >> > Which version of groovy behavior the documentation at
>> >> > http://groovy.codehaus.org/ is supposed to reflect - considering
>> >> > 1.5.x
>> >> > (in
>> >> > stable use), 1.6.x (mid-way) and 1.7.x(nearing a RC release) are all
>> >> > alive
>> >> > simultaneously and they have can have quite different behavior across
>> >> > versions at various places?
>> >> >
>> >> > rgds,
>> >> > Roshan
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Guillaume Laforge
>> >> Groovy Project Manager
>> >> Head of Groovy Development at SpringSource
>> >> http://www.springsource.com/g2one
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe from this list, please visit:
>> >>
>> >>    http://xircles.codehaus.org/manage_email
>> >>
>> >>
>> >
>> >
>>
>>
>>
>> --
>> Guillaume Laforge
>> Groovy Project Manager
>> Head of Groovy Development at SpringSource
>> http://www.springsource.com/g2one
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>

--
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Roshan Dawrani-2]

Thanks for sharing that.

On Sat, Nov 7, 2009 at 3:55 PM, Guillaume Laforge <glaforge@...> wrote:

The website is a kind of templated layer on top of the Confluence content.
And sometimes, you don't see the changes right away.
If you want to force the appearance of the change, you can append ?nc
to the end of the (website) URL.

On Sat, Nov 7, 2009 at 11:23, Roshan Dawrani <roshandawrani@...> wrote:
> Ok.
>
> Last question on this for now:
>
> Is the way to update the http://groovy.codehaus.org/ documentation to use
> the wiki at http://docs.codehaus.org/display/GROOVY/ and publish the
> content? They synch-up immediately? Or, is there any content-change approval
> step in between?
>
> -- Roshan
>
> On Sat, Nov 7, 2009 at 3:44 PM, Guillaume Laforge <glaforge@...>
> wrote:
>>
>> Yes, it's not easy to properly reflect the differences or new features
>> between version.
>> The idea is to just note the differences in the documentation as they
>> arise.
>>
>> On Sat, Nov 7, 2009 at 10:03, Roshan Dawrani <roshandawrani@...>
>> wrote:
>> > That arrangement is a bit messy - because at a place where it's not
>> > mentioned what version the behavior is for, it is not clear whether it's
>> > because the behavior is common across all versions or whether it is just
>> > outdated and not updated.
>> >
>> > Lots of confusions/questions seem to be coming on the mailing-list
>> > because
>> > what is documented on the groovy website doesn't work a particular
>> > version
>> > of groovy and of-course, the documentation doesn't mention the version
>> > of
>> > groovy at that place.
>> >
>> > And when that happens, you don't know how to update the documentation -
>> > split one piece of documentation into say 4 - one for each version of
>> > groovy? :-)
>> >
>> > -- Roshan
>> >
>> > On Sat, Nov 7, 2009 at 2:01 PM, Guillaume Laforge
>> > <glaforge@...>
>> > wrote:
>> >>
>> >> Hi Roshan,
>> >>
>> >> Ideally, we would have two different wikis, or different sections for
>> >> each version.
>> >> But so far, what we've done is indicating that this or that paragraph,
>> >> section or feature is about version x or y of Groovy, to indicate the
>> >> difference.
>> >>
>> >> Guillaume
>> >>
>> >> On Sat, Nov 7, 2009 at 06:32, Roshan Dawrani
>> >> <roshandawrani@...>
>> >> wrote:
>> >> > Hi,
>> >> > A basic doubt on groovy's documentation at
>> >> > http://groovy.codehaus.org/.
>> >> >
>> >> > Which version of groovy behavior the documentation at
>> >> > http://groovy.codehaus.org/ is supposed to reflect - considering
>> >> > 1.5.x
>> >> > (in
>> >> > stable use), 1.6.x (mid-way) and 1.7.x(nearing a RC release) are all
>> >> > alive
>> >> > simultaneously and they have can have quite different behavior across
>> >> > versions at various places?
>> >> >
>> >> > rgds,
>> >> > Roshan
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Guillaume Laforge
>> >> Groovy Project Manager
>> >> Head of Groovy Development at SpringSource
>> >> http://www.springsource.com/g2one
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe from this list, please visit:
>> >>
>> >>    http://xircles.codehaus.org/manage_email
>> >>
>> >>
>> >
>> >
>>
>>
>>
>> --
>> Guillaume Laforge
>> Groovy Project Manager
>> Head of Groovy Development at SpringSource
>> http://www.springsource.com/g2one
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>

--

Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email