deepakpanda93 commented on code in PR #19581:
URL: https://github.com/apache/hudi/pull/19581#discussion_r3860094705


##########
website/src/pages/roadmap.md:
##########
@@ -11,53 +11,49 @@ down by areas on our [stack](/docs/hudi_stack).
 
 ## Recent Release(s)
 
-[1.1.1](/releases/release-1.1#release-111) (Dec 2025)
+[1.2.0](/releases/release-1.2#release-120) (May 2026)
 
 ## Future Releases
 
 | Release | Timeline  |
 |---------|-----------|
-| 1.2.0   | Jan 2026  |
-| 2.0.0   | Jun 2026  |
+| 1.2.1   | Aug 2026  |
+| 1.3.0   | Sep 2026  |
+| 2.0.0   | Dec 2026  |
 
 ## Storage Engine
 
 | Feature                                              | Target Release | 
Tracking                                                                        
                                                                                
               |
 
|------------------------------------------------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Introduce `.abort` state in the timeline             | 1.2.0          | 
[#16609](https://github.com/apache/hudi/issues/16609) |
-| Variant type support on Spark 4                      | 1.2.0          | 
[#16851](https://github.com/apache/hudi/issues/16851) |
-| Non-blocking updates during clustering               | 1.2.0          | 
[#14611](https://github.com/apache/hudi/issues/14611)                           
                                                                                
        |
-| Enable partial updates for CDC workload payload      | 1.2.0          | 
[#16354](https://github.com/apache/hudi/issues/16354)                           
                                                                                
        |
-| Schema tracking in metadata table                    | 1.2.0          | 
[#14397](https://github.com/apache/hudi/issues/14397) |
-| NBCC for MDT writes                                  | 1.2.0          | 
[#17305](https://github.com/apache/hudi/issues/17305) |
-| Index abstraction for writer and reader              | 1.2.0          | 
[#16903](https://github.com/apache/hudi/issues/16903) |
-| Vector search index                                  | 1.2.0          | 
[#16852](https://github.com/apache/hudi/issues/16852) |
-| Bitmap index                                         | 1.2.0          | 
[#16853](https://github.com/apache/hudi/issues/16853) |
-| New abstraction for schema, expressions, and filters | 1.2.0          | 
[RFC-88](https://github.com/apache/hudi/pull/12795) |
-| Streaming CDC/Incremental read improvement           | 1.2.0          | 
[#14916](https://github.com/apache/hudi/issues/14916) |
-| Supervised table service planning and execution      | 1.2.0          | 
[RFC-43](https://github.com/apache/hudi/pull/4309), 
[#15196](https://github.com/apache/hudi/issues/15196)                           
                                    |
-| General purpose support for multi-table transactions | 1.2.0          | 
[#16181](https://github.com/apache/hudi/issues/16181) |
-| Supporting different updated columns in a single partial update log file | 
1.2.0          | [#16854](https://github.com/apache/hudi/issues/16854) |
-| CDC format consolidation                             | 1.2.0          | 
[#16429](https://github.com/apache/hudi/issues/16429) |
+| Introduce `.abort` state in the timeline             | 1.2.1          | 
[#16609](https://github.com/apache/hudi/issues/16609) |
+| Non-blocking updates during clustering               | 1.2.1          | 
[#14611](https://github.com/apache/hudi/issues/14611)                           
                                                                                
        |
+| Enable partial updates for CDC workload payload      | 1.2.1          | 
[#16354](https://github.com/apache/hudi/issues/16354)                           
                                                                                
        |
+| Schema tracking in metadata table                    | 1.2.1          | 
[#14397](https://github.com/apache/hudi/issues/14397) |
+| Index abstraction for writer and reader              | 1.2.1          | 
[#16903](https://github.com/apache/hudi/issues/16903) |
+| New abstraction for schema, expressions, and filters | 1.2.1          | 
[RFC-88](https://github.com/apache/hudi/pull/12795) |
+| Streaming CDC/Incremental read improvement           | 1.2.1          | 
[#14916](https://github.com/apache/hudi/issues/14916) |
+| Supervised table service planning and execution      | 1.2.1          | 
[RFC-43](https://github.com/apache/hudi/pull/4309), 
[#15196](https://github.com/apache/hudi/issues/15196)                           
                                    |
+| General purpose support for multi-table transactions | 1.2.1          | 
[#16181](https://github.com/apache/hudi/issues/16181) |

Review Comment:
   Done in 690984769e44 — every feature row now targets 1.3.0.
   
   This settles a question that had been open on the PR since the first review 
round, so thanks for the clear call. 21 rows moved: 11 in Storage Engine, 2 in 
Programming APIs, 4 in Query Engine Integration, 3 in Platform Components, plus 
the Developer Experience row that is now removed per your other comment.
   
   One deliberate choice worth confirming: I left **1.2.1 in the Future 
Releases table**. It is still a planned release with a timeline, so removing it 
would lose real information; it now simply has nothing targeting it, which is 
exactly the point you are making about a minor release not carrying new 
features. Say the word if you would rather the table only list releases that 
carry roadmap items.
   
   For the record, `1.2.1` now appears exactly once on the page, in that Future 
Releases row, and no feature row references it.



-- 
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