-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[docs] added touchups to readme.md #354
base: main
Are you sure you want to change the base?
Conversation
@om-raheja is attempting to deploy a commit to the AIOS Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The v0.2.0.beta version is used to tag and package code to a stable version without changing, and the 0.2.0.beta is currently used for testing. Once the testing is completed, it will be taged and released as v0.2.0.
But is that really necessary for the average person who wants to get
started as fast as possible and get working on the project?
…On Sat Nov 30, 2024 at 3:07 PM EST, Kai Mei wrote:
@dongyuanjushi commented on this pull request.
The v0.2.0.beta version is used to tag and package code to a stable version without changing, and the 0.2.0.beta is currently used for testing.
|
It might be more helpful to add an instruction here to indicate that it is recommended to use the stable version (v0.2.0.beta for example) instead of removing the git checkout -b v0.2.0.beta? |
Sounds good, done.
…On Sat Nov 30, 2024 at 10:01 PM EST, Kai Mei wrote:
> But is that really necessary for the average person who wants to get started as fast as possible and get working on the project?
> […](#)
> On Sat Nov 30, 2024 at 3:07 PM EST, Kai Mei wrote: @dongyuanjushi commented on this pull request. The v0.2.0.beta version is used to tag and package code to a stable version without changing, and the 0.2.0.beta is currently used for testing.
It might be more helpful to add an instruction here to indicate that it is recommended to use the stable version (v0.2.0.beta for example) instead of removing the git checkout -b v0.2.0.beta?
|
Could you change your current changes of git checkout v.20 to git checkout v0.2.0.beta (v0.2.0.beta is the correct tag that needs to be switched to)? |
This change is a documentation change that remove the requirement to use
git checkout v.20
and clears up certain information on theREADME.md
that confused me when I first started.