[
https://issues.apache.org/jira/browse/CASSANDRA-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628664#comment-17628664
]
Erick Ramirez commented on CASSANDRA-18014:
-------------------------------------------
I’ve completed final verification in staging and [published to
production|https://github.com/apache/cassandra-website#merging-asf-staging-to-asf-site]:
{noformat}
$ git branch
* trunk
$ git fetch origin
$ git checkout asf-site
Branch ‘asf-site’ set up to track remote branch ‘asf-site’ from ‘origin’.
Switched to a new branch ‘asf-site’
$ git branch
* asf-site
trunk
$ git reset --hard origin/asf-staging
HEAD is now at a3f6c10c generate docs for 8e4e9469
$ git push -f origin asf-site
Total 0 (delta 0), reused 0 (delta 0)
To [https://github.com/apache/cassandra-website.git]
+ 4603a308...a3f6c10c asf-site -> asf-site (forced update)
{noformat}
The blog post is now live on the site –
https://cassandra.apache.org/_/blog/Apache-Cassandra-Changelog-20-November-2022.html
> WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
> -------------------------------------------------------------
>
> Key: CASSANDRA-18014
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18014
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
> Reporter: Diogenese Topper
> Assignee: Chris Thornett
> Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
> Attachments: c18014-01-blog-index.png, c18014-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the November
> 2022 blog "Apache Cassandra Changelog #20"
> If this blog cannot be published by the November 3, 2022 publish date, please
> contact me, suggest changes, or correct the date when possible in the pull
> request for the appropriate time that the blog will go live (on both the blog
> page card and the post).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
