On 20 Sep 2016, at 10:03, Guillaume Delhumeau
<guillaume.delhumeau(a)xwiki.com> wrote:
2016-09-19 18:52 GMT+02:00 Vincent Massol <vincent(a)massol.net>et>:
On 19 Sep 2016, at 16:02, Ecaterina Moraru
(Valica) <valicac(a)gmail.com>
wrote:
ExtensionVersionClass
?
Because it’s very different! Actually there isn’t a single field that is
the same as my ChangesClass :)
Maybe the difference is that this is per version
and you kind of want per
functionality.
But the 'Category' is not needed, since we have the extension page name.
The idea is that I would really want us to see if we could use this
application also in the future, to document things for the extensions
pages.
So, for this, I’ve added the notion of ‘Product” to the app.
Can it takes multiple arguments? For instance, we develop 4 products:
contrib, rendering, platform and enterprise.
Well I haven’t coded the filtering on product in the macro yet but we could imagine
supporting a comma-separated list of product names yes.
Thanks
-Vincent
So you can now use it for the release notes of any
number of products (and
> thus including for extensions with a separate versioning and release cycle).
>
> We could imagine the extension page using the {{changes/}} macro to
> display the RN, or point with a link to the RN page for that product (i.e.
> extension).
>
> Thanks
> -Vincent
>
>> Thanks,
>> Caty
>
> [snip]