On Mon, Jun 4, 2012 at 10:24 AM, Vincent Massol <[email protected]> wrote:

Hi devs,

I'd like to propose that we:

1) always add explanations in our pom.xml files when we add CLIRR excludes (since we should have any based on our deprecation/legacy rule) 2) copy them in our release notes.

As an example I've just done that for http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterprise...

The advantage: * Users get an explanation as to why we have broken some APIs * We need the explanation in our pom.xml for ourselves to understand why we're excluding some files and since we have that explanation we might as well copy it to the release notes…

WDYT?

+1

Thanks -Vincent

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

-- Thomas Mortagne

+1 Thanks, Marius On Mon, Jun 4, 2012 at 11:24 AM, Vincent Massol <[email protected]> wrote:

Hi devs,

I'd like to propose that we:

1) always add explanations in our pom.xml files when we add CLIRR excludes (since we should have any based on our deprecation/legacy rule) 2) copy them in our release notes.

As an example I've just done that for http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterprise...

The advantage: * Users get an explanation as to why we have broken some APIs * We need the explanation in our pom.xml for ourselves to understand why we're excluding some files and since we have that explanation we might as well copy it to the release notes…

WDYT?

Thanks -Vincent

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs