20 Oct
2010
20 Oct
'10
11:29 p.m.
On 14 oct. 2010, at 22:52, Sergiu Dumitriu wrote:
On 10/14/2010 10:02 PM, Paul Libbrecht wrote:
As I said, as long as curriki itself doesn't have paths (svn or maven) that are with
retired, I'm fine.
Hence here's my +1.
paul
On 14 oct. 2010, at 19:10, Caleb James DeLisle wrote:
But that would really mean the project curriki is retired or retiring.
I think this is not correct.
No, it means that the Curriki project is doing fine with the current
versions of the plugins. And these versions are in the maven repository,
and will always be there. Moving the code to the retired svn repository
means just that no new development is planned for them. And, if Curriki
wants to evolve, then it should upgrade to a newer version of the
platform, and it should switch to components, which means new modules,
not related to the plugins. Your
proposal says "move Curriki to retired" ?
Oops, indeed it does. I meant
move only xwiki-plugin-invitationmanager and xwiki-plugin-spacemanager.
My proposal is that the historical maven builds will remain and the source will still be
avainable
in the contrib/retired section but no new builds will be created by hudson.