On Thu, Jun 16, 2016 at 10:43 AM, Eduard Moraru <enygma2002(a)gmail.com> wrote:
+1
Also, if we retire the jira project, it means that we stop the support for
this application (since no new issues can be created), effectively retiring
the whole application itself, not only its jira project.
I`m not sure if we currently have a documented process for retiring contrib
extensions, but we should at least update the descriptions (and maybe title
as well - marking it [Retired]) on the e.x.o. page and on the contrib repo
to clearly mention that the app is no longer actively supported by anyone.
We don't have any process. We actually never done it before. What we
could easily do is add a property in ExtensionClass to indicate an
extension is retired in which case:
* the extension does not appear in EM anymore (i.e. make the extension
"invalid") since that's something we want for this kind of extension I
think
* the extension sheet make clear it's retired with some visible marker
in the title and some warning at the beginning of the content
P.S.: The link to the new old jira project would still need to be added to
the e.x.o page since it`s currently missing.
Thanks,
Eduard
On Thu, Jun 16, 2016 at 10:20 AM, Alexandru Cotiuga <
alexandru.cotiuga(a)xwiki.com> wrote:
Hi devs,
Currently, the Meeting Manager Application [
http://extensions.xwiki.org/xwiki/bin/view/Extension/Meeting+Manager+Applic…
]
is marked, with a warning, as "This application is superseded by the
Meeting
Application". The application is written in xwiki/1.0 syntax and is full of
deprecated usages which makes it unusable at least since XWiki 6.2.
Considering the above reasons I propose to retire the MEETING Jira project.
Thanks,
Alex
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne