[ 
https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627886#comment-17627886
 ] 

Ekaterina Dimitrova edited comment on CASSANDRA-17976 at 11/2/22 6:30 PM:
--------------------------------------------------------------------------

Thanks [~mck] , I am wondering whether we should remove those pages as some of 
them might be serving also as docs? I was trying to identify a page for 
Streaming for example and I didn't manage to find one. Or maybe we can put 
those in the blog?

Can we also move the config doc link (the one that was removed) under the 
Config section or should I open a new ticket for that? 


was (Author: e.dimitrova):
Thanks [~mck] , I am wondering whether we should remove those pages as some of 
them might be serving also as docs? I was trying to identify a page for 
Streaming for example and I didn't manage to find one. Or maybe we can put 
those in the blog?

Can we also move the config doc link under the Config section or should I open 
a new ticket for that? 

> Update What's New Page in Cassandra Website - 4.1 and trunk
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-17976
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17976
>             Project: Cassandra
>          Issue Type: Task
>          Components: Legacy/Documentation and Website
>            Reporter: Ekaterina Dimitrova
>            Assignee: Michael Semb Wever
>            Priority: Low
>             Fix For: 4.1.x, 4.x
>
>
> [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html]
> The page still says 4.0 and lists 4.0 new developments.
> We need to point to 4.1 and list latest developments blog posts, docs; 
> probably we can also link NEWS.txt and CHANGES.txt



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to