hechao-ustc opened a new pull request, #456:
URL: https://github.com/apache/paimon-rust/pull/456

   <!--
   Thank you very much for contributing to Paimon Rust - we are happy that you 
want to help us improve it. To help the community review your contribution in 
the best possible way, please go through the checklist below, which will get 
the contribution into a shape in which it can be best reviewed.
   
   ## Contribution Checklist
   
     - Make sure that the pull request corresponds to a [GitHub 
issue](https://github.com/apache/paimon-rust/issues). Exceptions are made for 
typos in documentation or comments, which need no issue.
   
     - Fill out the template below to describe the changes contributed by the 
pull request. That will give reviewers the context they need to do the review.
   
     - Make sure that the change passes the automated tests, i.e., `cargo test` 
passes.
   
     - Each pull request should address only one issue, not mix up code from 
multiple issues.
   
   **(The sections below can be removed for hotfixes or typos)**
   -->
   
   ### Purpose
   The workspace version is `0.3.0` (Cargo.toml:22), but user-facing 
installation examples still reference `0.1.0`, and the project status claims to 
track the `0.1.0 milestone`. This misleads new users into depending on an 
outdated release.
   <!-- Linking this pull request to the issue -->
   
   <!-- What is the purpose of the change -->
   
    ### Changes                                                                 
                                                                                
         
   
     - Bump installation examples from `"0.1.0"` to `"0.2.0"` (current release) 
in `getting-started.md` and `sql.md` (10 locations total)                       
            
     - Update project status from `tracking the 0.1.0 milestone` to `0.3.0 in 
development` in `index.md`
   


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