yihua commented on code in PR #11491:
URL: https://github.com/apache/hudi/pull/11491#discussion_r1650168114


##########
website/src/pages/roadmap.md:
##########
@@ -8,64 +8,68 @@ Hudi community strives to deliver major releases every 3-4 
months, while offerin
 This page captures the forward-looking roadmap of ongoing & upcoming projects 
and when they are expected to land, broken
 down by areas on our 
[stack](blog/2021/07/21/streaming-data-lake-platform/#hudi-stack).
 
+## Recent Release
+[0.15.0](https://issues.apache.org/jira/projects/HUDI/versions/12353381) (June 
2024)

Review Comment:
   Should we use the release link in the website, i.e., 
https://hudi.apache.org/releases/release-0.15.0?



##########
website/src/pages/roadmap.md:
##########
@@ -8,64 +8,68 @@ Hudi community strives to deliver major releases every 3-4 
months, while offerin
 This page captures the forward-looking roadmap of ongoing & upcoming projects 
and when they are expected to land, broken
 down by areas on our 
[stack](blog/2021/07/21/streaming-data-lake-platform/#hudi-stack).
 
+## Recent Release
+[0.15.0](https://issues.apache.org/jira/projects/HUDI/versions/12353381) (June 
2024)
+
 ## Future Releases
 
-Next upcoming release : 
[0.14.1](https://issues.apache.org/jira/projects/HUDI/versions/12353493) (Dec 
2023)
+- 
[1.0.0-beta2](https://issues.apache.org/jira/projects/HUDI/versions/12354810) 
(July 2024)
+- [0.16.0](https://issues.apache.org/jira/projects/HUDI/versions/12354773) - 
Bridge release supporting reads of both 1.x and 0.x Hudi versions. (Q3, 2024)
+- [1.0.0](https://issues.apache.org/jira/projects/HUDI/versions/12353848) (Q3, 
2024)

Review Comment:
   These links are not publicly accessible somehow.  Could you check them again 
or remove them?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to