Staging the 1.11.0 website updates

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Staging the 1.11.0 website updates

Julian Foad-5
I just pushed the website updates for 1.11.0 to staging:

https://subversion-staging.apache.org/
https://subversion-staging.apache.org/news
https://subversion-staging.apache.org/download
https://subversion-staging.apache.org/docs/release-notes/release-history.html
https://subversion-staging.apache.org/doap  (is not HTML)

Please review if you have a mind to.

I hope to be able to publish tomorrow 30th Oct (that's the date I've put in the website and CHANGES file in the tarball) which would be possible if we can get 3 signatures today, or at the very latest the day after (which would be close enough for the discrepancy not to matter, and would still achieve our stated October release date target).

--
- Julian
Reply | Threaded
Open this post in threaded view
|

Re: Staging the 1.11.0 website updates

Julian Foad-6
Can someone add to staging : remove WIP banner from release notes? (I can get to it later but AFK now.)
- Julian
Reply | Threaded
Open this post in threaded view
|

Re: Staging the 1.11.0 website updates

Julian Foad-5
Julian Foad wrote:
> Can someone add to staging : remove WIP banner from release notes? (I
> can get to it later but AFK now.)

Done in r1845177.

--
- Julian
Reply | Threaded
Open this post in threaded view
|

Re: Staging the 1.11.0 website updates

Branko Čibej
In reply to this post by Julian Foad-5
On 29.10.2018 18:43, Julian Foad wrote:

> I just pushed the website updates for 1.11.0 to staging:
>
> https://subversion-staging.apache.org/
> https://subversion-staging.apache.org/news
> https://subversion-staging.apache.org/download
> https://subversion-staging.apache.org/docs/release-notes/release-history.html
> https://subversion-staging.apache.org/doap  (is not HTML)
>
> Please review if you have a mind to.
>
> I hope to be able to publish tomorrow 30th Oct (that's the date I've put in the website and CHANGES file in the tarball) which would be possible if we can get 3 signatures today, or at the very latest the day after (which would be close enough for the discrepancy not to matter, and would still achieve our stated October release date target).


Looks good, after a rather cursory glance.

-- Brane
Reply | Threaded
Open this post in threaded view
|

Re: Staging the 1.11.0 website updates

Nathan Hartman
On 29.10.2018 18:43, Julian Foad wrote:
> I just pushed the website updates for 1.11.0 to staging:
>
> https://subversion-staging.apache.org/
> https://subversion-staging.apache.org/news
> https://subversion-staging.apache.org/download
> https://subversion-staging.apache.org/docs/release-notes/release-history.html
> https://subversion-staging.apache.org/doap  (is not HTML)
>
> Please review if you have a mind to.
>
> I hope to be able to publish tomorrow 30th Oct (that's the date I've put in the website and CHANGES file in the tarball) which would be possible if we can get 3 signatures today, or at the very latest the day after (which would be close enough for the discrepancy not to matter, and would still achieve our stated October release date target).

Not a showstopper, but "Founded in 2000 by CollabNet, Inc., the Subversion project and software have seen incredible success over the past decade" should be changed to "last two decades" one of these days, no? Especially as someone pointed out earlier that Subversion is now of legal age. :-)


Reply | Threaded
Open this post in threaded view
|

Re: Staging the 1.11.0 website updates

Branko Čibej
In reply to this post by Branko Čibej
On 30.10.2018 17:11, Branko Čibej wrote:

> On 29.10.2018 18:43, Julian Foad wrote:
>> I just pushed the website updates for 1.11.0 to staging:
>>
>> https://subversion-staging.apache.org/
>> https://subversion-staging.apache.org/news
>> https://subversion-staging.apache.org/download
>> https://subversion-staging.apache.org/docs/release-notes/release-history.html
>> https://subversion-staging.apache.org/doap  (is not HTML)
>>
>> Please review if you have a mind to.
>>
>> I hope to be able to publish tomorrow 30th Oct (that's the date I've put in the website and CHANGES file in the tarball) which would be possible if we can get 3 signatures today, or at the very latest the day after (which would be close enough for the discrepancy not to matter, and would still achieve our stated October release date target).
>
> Looks good, after a rather cursory glance.


Oops. I was just reminded in IRC that we did not update the API doc
links in the last two .0 releases:

https://subversion-staging.apache.org/docs/

We should have statically  generated pages for the API docs committed to
the site tree.

-- Brane

Reply | Threaded
Open this post in threaded view
|

Re: Staging the 1.11.0 website updates

Julian Foad-5
Branko Čibej wrote:
> Oops. I was just reminded in IRC that we did not update the API doc
> links in the last two .0 releases:
>
> https://subversion-staging.apache.org/docs/
>
> We should have statically  generated pages for the API docs committed to
> the site tree.

I'm doing that right now: adding 1.10 in 'publish' and 1.11 in 'staging'.

I commented out your section of links to latest trunk docs ( http://subversion.a.o.local/docs/#next-release ), as those are currently not being built.

--
- Julian
Reply | Threaded
Open this post in threaded view
|

Re: Staging the 1.11.0 website updates

Branko Čibej
On 30.10.2018 22:32, Julian Foad wrote:

> Branko Čibej wrote:
>> Oops. I was just reminded in IRC that we did not update the API doc
>> links in the last two .0 releases:
>>
>> https://subversion-staging.apache.org/docs/
>>
>> We should have statically  generated pages for the API docs committed to
>> the site tree.
> I'm doing that right now: adding 1.10 in 'publish' and 1.11 in 'staging'.
>
> I commented out your section of links to latest trunk docs ( http://subversion.a.o.local/docs/#next-release ), as those are currently not being built.

Perfect, thanks ... I'd started setting that up on svn-qavm3, but ...
well, let's say I got sidetracked, eh.

-- Brane