[ 
https://issues.apache.org/jira/browse/CASSANDRA-17066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Diogenese Topper updated CASSANDRA-17066:
-----------------------------------------
    Description: 
This ticket is to capture the work associated with publishing the November 2021 
blog post titled "Harry, an Open Source Fuzz Testing and Verification Tool for 
Apache Cassandra."

If this blog cannot be published by the November 9 publish date, please be sure 
to *correct the date* before going live.

This ticket can be closed once the blog post has gone live on the website.

  was:
This ticket is to capture the work associated with publishing the November 2021 
blog post titled "Harry, an Open Source Fuzz Testing and Verification Tool for 
Apache Cassandra."

If this blog cannot be published by the November 9 publish date, please be sure 
to *correct the date* before going live.


> Blog post: "Harry: A Fuzz Testing Tool for Apache Cassandra"
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-17066
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17066
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Documentation/Blog
>            Reporter: Alex Petrov
>            Assignee: Alex Petrov
>            Priority: Normal
>              Labels: pull-request-available
>             Fix For: 4.0.2, 4.1
>
>
> This ticket is to capture the work associated with publishing the November 
> 2021 blog post titled "Harry, an Open Source Fuzz Testing and Verification 
> Tool for Apache Cassandra."
> If this blog cannot be published by the November 9 publish date, please be 
> sure to *correct the date* before going live.
> This ticket can be closed once the blog post has gone live on the website.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to