The CMS going away does not affect svnpubsub/subversion.
Andrew
On Thu, Aug 20, 2020 at 4:46 PM Manfred Moser
wrote:
> I guess we just need confirmation that the fact that CMS goes away does
> not include svnpubsub/subversion...
>
> Manfred
>
>
> Hervé BOUTEMY wrote on 2020-08-20 12:21 (GMT -07
I guess we just need confirmation that the fact that CMS goes away does not
include svnpubsub/subversion...
Manfred
Hervé BOUTEMY wrote on 2020-08-20 12:21 (GMT -07:00):
> (forgot to cc infra)
>
> sorry, I completely overlooked the discussion during PTO...
>
> I worked with Gav in the past
(forgot to cc infra)
sorry, I completely overlooked the discussion during PTO...
I worked with Gav in the past to go from rsync to CMS, then go out of CMS to
direct svnpubsub+maven-scm-publish-plugin [1]: we don't use CMS at all any
more for a few years
Regards,
Hervé
[1] https://maven.apach
sorry, I completely overlooked the discussion during PTO...
I worked with Gav in the past to go from rsync to CMS, then go out of CMS to
direct svnpubsub+maven-scm-publish-plugin [1]: we don't use CMS at all any
more for a few years
Regards,
Hervé
[1] https://maven.apache.org/developers/websi
Hi:
Yes: I am referring to you creating content in the CMS, which the CMS then
uses to update your project's static website. The CMS is reaching
end-of-life, and we need projects to migrate to a different static-site
generator.
Andrew
On Wed, Aug 19, 2020 at 10:33 PM Olivier Lamy wrote:
> Hi A
I think you guys are fine and there is nothing to do. We still have some
Maven configs in our CMS system but looks like you have not used it since
2018.
I'll go ahead and remove your old CMS content and configs
Gav...
On Thu, Aug 20, 2020 at 6:23 AM Manfred Moser
wrote:
> Also ... from a tech
asfgit merged pull request #37:
URL: https://github.com/apache/maven-doxia/pull/37
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to t
