You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Roger Leigh <rl...@codelibre.net> on 2020/05/12 20:34:23 UTC
Releasing Xalan-C++ 1.12
Hi folks,
I have commit access to the source repository, but it seems I don't have
access to the website at
http://svn.apache.org/repos/asf/xalan/site/docs/xalan/xalan-c
Would it be possible to be permitted access?
The reason for this is that I would like, as a prerequisite to making a
1.12 release, to make the new documentation at
https://apache.github.io/xalan-c/ the official documentation and API
reference for the project. As such, I would like to place a .htaccess
file with suitable redirects on the website so that all of the
documentation links redirect to the new pages for the 1.12 release.
Additionally, I might need write access to add the release artefacts at
https://dist.apache.org/repos/dist/release/xalan/xalan-c/
Would it be possible to grant access to this as well?
Many thanks,
Roger Leigh
Re: Releasing Xalan-C++ 1.12
Posted by Roger Leigh <rl...@codelibre.net>.
On 13/05/2020 15:50, Bill Blough wrote:
> On Wed, May 13, 2020 at 08:29:47AM +0100, Roger Leigh wrote:
>> To follow up,
>>
>>
>> I have been able to commit and push to xalan-site (git). However, I'm not
>> sure that directly affected the production website. I assume there's some
>> job which updates the site from version control, but I don't know if that's
>> been updated to work with the new git repo. Does anyone know how this
>> works, and who is responsible for it?
> As I understand it, it's all controlled by the .asf.yaml configuration [1].
> So pushing a .asf.yaml file with the appropriate config to the
> appropriate branch should make it happen automatically from that point
> forward.
>
> Though, looking at the docs, it doesn't seem possible to specify an arbitrary
> directory to deploy from, so we might have to move the contents of docs/xalan
> to /content or /output to make it work correctly.
>
>
> A .asf.yaml with
>
>
> publish:
> whoami: master
>
>
> committed to the root of master and docs/xalan moved to /content should do
> the trick, I think.
>
>
> [1]https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories
>
Thanks Bill, that's now working.
I couldn't get it to work from a /content directory, even with pelican
enabled which is what the linked docs say it's for. As a result I moved
all the content to the root, and the website is still being served OK.
If I could find out how to do that then I could look at moving the
content from gh-pages directly to the xalan-site repository. Though it
might well require the root page to be converted to markdown, too. I
didn't want to mess with that for now. However, if there are no
objections to dropping stylebook in favour of simple markdown, I'll be
happy to convert that--it's only a single page plus some links. It
might not look as nice though; I'm no designer.
Kind regards,
Roger
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: Releasing Xalan-C++ 1.12
Posted by Bill Blough <de...@blough.us.INVALID>.
On Wed, May 13, 2020 at 08:29:47AM +0100, Roger Leigh wrote:
> To follow up,
>
>
> I have been able to commit and push to xalan-site (git). However, I'm not
> sure that directly affected the production website. I assume there's some
> job which updates the site from version control, but I don't know if that's
> been updated to work with the new git repo. Does anyone know how this
> works, and who is responsible for it?
As I understand it, it's all controlled by the .asf.yaml configuration [1].
So pushing a .asf.yaml file with the appropriate config to the
appropriate branch should make it happen automatically from that point
forward.
Though, looking at the docs, it doesn't seem possible to specify an arbitrary
directory to deploy from, so we might have to move the contents of docs/xalan
to /content or /output to make it work correctly.
A .asf.yaml with
publish:
whoami: master
committed to the root of master and docs/xalan moved to /content should do
the trick, I think.
[1]https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories
--
GPG: 5CDD 0C9C F446 BC1B 2509 8791 1762 E022 7034 CF84
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: Releasing Xalan-C++ 1.12
Posted by Roger Leigh <rl...@codelibre.net>.
To follow up,
I have been able to commit and push to xalan-site (git). However, I'm
not sure that directly affected the production website. I assume
there's some job which updates the site from version control, but I
don't know if that's been updated to work with the new git repo. Does
anyone know how this works, and who is responsible for it?
Thanks again,
Roger
On 13/05/2020 08:14, Roger Leigh wrote:
>
> Hi Bill,
>
>
> Thanks for the pointer, I didn't realise that this had also been
> converted. I'll clone it and see if I have permission to make changes.
>
>
> Thanks again,
>
> Roger
>
>
> On 13/05/2020 00:51, Bill Blough wrote:
>> Hi Roger,
>>
>> On Tue, May 12, 2020 at 09:34:23PM +0100, Roger Leigh wrote:
>>> Hi folks,
>>>
>>>
>>> I have commit access to the source repository, but it seems I don't have
>>> access to the website at
>>> http://svn.apache.org/repos/asf/xalan/site/docs/xalan/xalan-c
>>>
>>> Would it be possible to be permitted access?
>>>
>>> The reason for this is that I would like, as a prerequisite to making a 1.12
>>> release, to make the new documentation athttps://apache.github.io/xalan-c/
>>> the official documentation and API reference for the project. As such, I
>>> would like to place a .htaccess file with suitable redirects on the website
>>> so that all of the documentation links redirect to the new pages for the
>>> 1.12 release.
>> I'm under the impression that the entire xalan SVN tree is read-only
>> since the move to github. We could probably get INFRA to toggle it, but
>> it might be quicker/easier to deploy it from the xalan-site git repo by
>> adding a .asf.yaml [1] file with the appropriate publishing settings.
>>
>> [1]https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories
>>
>>
>> Best regards,
>> Bill
>>
Re: Releasing Xalan-C++ 1.12
Posted by Roger Leigh <rl...@codelibre.net>.
Hi Bill,
Thanks for the pointer, I didn't realise that this had also been
converted. I'll clone it and see if I have permission to make changes.
Thanks again,
Roger
On 13/05/2020 00:51, Bill Blough wrote:
> Hi Roger,
>
> On Tue, May 12, 2020 at 09:34:23PM +0100, Roger Leigh wrote:
>> Hi folks,
>>
>>
>> I have commit access to the source repository, but it seems I don't have
>> access to the website at
>> http://svn.apache.org/repos/asf/xalan/site/docs/xalan/xalan-c
>>
>> Would it be possible to be permitted access?
>>
>> The reason for this is that I would like, as a prerequisite to making a 1.12
>> release, to make the new documentation at https://apache.github.io/xalan-c/
>> the official documentation and API reference for the project. As such, I
>> would like to place a .htaccess file with suitable redirects on the website
>> so that all of the documentation links redirect to the new pages for the
>> 1.12 release.
>
> I'm under the impression that the entire xalan SVN tree is read-only
> since the move to github. We could probably get INFRA to toggle it, but
> it might be quicker/easier to deploy it from the xalan-site git repo by
> adding a .asf.yaml [1] file with the appropriate publishing settings.
>
> [1] https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories
>
>
> Best regards,
> Bill
>
Re: Releasing Xalan-C++ 1.12
Posted by Bill Blough <bi...@apache.org>.
Hi Roger,
On Tue, May 12, 2020 at 09:34:23PM +0100, Roger Leigh wrote:
> Hi folks,
>
>
> I have commit access to the source repository, but it seems I don't have
> access to the website at
> http://svn.apache.org/repos/asf/xalan/site/docs/xalan/xalan-c
>
> Would it be possible to be permitted access?
>
> The reason for this is that I would like, as a prerequisite to making a 1.12
> release, to make the new documentation at https://apache.github.io/xalan-c/
> the official documentation and API reference for the project. As such, I
> would like to place a .htaccess file with suitable redirects on the website
> so that all of the documentation links redirect to the new pages for the
> 1.12 release.
I'm under the impression that the entire xalan SVN tree is read-only
since the move to github. We could probably get INFRA to toggle it, but
it might be quicker/easier to deploy it from the xalan-site git repo by
adding a .asf.yaml [1] file with the appropriate publishing settings.
[1] https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories
Best regards,
Bill
--
GPG: 5CDD 0C9C F446 BC1B 2509 8791 1762 E022 7034 CF84
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org