We could have an "Extensions" section in the RN of XE where we could
display noticeable functionalities. So that's your 1) variant.
My problem is that we have this discrepancy between RN and Documentation.
So this means we would duplicate content to RN and Documentation, instead
of reusing it. Usually instead of duplicating it, we just put it in one
place and link from the other. Maybe the "News and Worthy" application
could improve this. Have some ReleaseNotes objects per version that could
be integrated inside XE RN and Extensions documentation, and use them from
the XE RN.
On Mon, Sep 19, 2016 at 4:51 PM, Marius Dumitru Florea <
> +1 for 1)
> On Tue, Sep 13, 2016 at 7:23 PM, Vincent Massol <vinc...@massol.net>
> > Hi devs,
> > We now include a few contrib apps in XE. However, when someone checks the
> > RN for XE, for example http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/
> > ReleaseNotesXWiki83M2 all they see is this:
> > “The following dependencies have been upgraded:
> > * Tour Application 1.0.4”
> > It doesn’t say if there are any substantial things added those deps.
> > I can think of 2 solutions:
> > 1) When something is noticeable, add it to the RN of XE. So for example
> > CKEditor extension adds something new, users checking the RN of XE can
> > it immediately.
> > 2) Link to the RN of the extension. However RN of extensions on e.x.o are
> > not nice. They’re just lists of JIRA issues. So for this solution to be a
> > bit satisfactory we would need to improve the RN of extensions, starting
> > with those we bundle in XE. Another possibility is to say that for
> > Recommended Extensions we pay an extra care to write nice Release Notes.
> > But that’s harder to enforce and ensure.
> > Option 1) is my preference.
> > WDYT?
> > Thanks
> > -Vincent
> > _______________________________________________
> > devs mailing list
> > email@example.com
> > http://lists.xwiki.org/mailman/listinfo/devs
> devs mailing list
devs mailing list