Skip to content
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

Figure out optimal strategy for version control #17

Open
novusnota opened this issue Apr 3, 2024 · 0 comments
Open

Figure out optimal strategy for version control #17

novusnota opened this issue Apr 3, 2024 · 0 comments
Assignees
Labels
bug Something isn't working or doesn't seem right priority: highest What should be done first and foremost

Comments

@novusnota
Copy link
Member

novusnota commented Apr 3, 2024

For users to be able to specify dev/nightly/main for the latest updates and stable/release (or a particular Tact version tag). Then, update all the plugin configurations in the README.md and in docs, when they arrive in #7.

Otherwise, everyone's going to get the dev Tact syntax, which is ahead of the released ones, because I plan on keeping all the editor integrations of my creation (this one, soon-to-be-made Sublime Text package, and possibly others) and tree-sitter-tact in sync with the main branch of Tact compiler.

UPD: Consider adding a message on start-up if the flag let g:tact_prefer_legacy is not set — "Tact.vim was drastically updated and integrated with an LSP. Please, refer to instructions in README.md on https:/tact-lang/tact.vim"

P.S.: just do semver releases?

@novusnota novusnota added the bug Something isn't working or doesn't seem right label Apr 3, 2024
@novusnota novusnota self-assigned this Apr 3, 2024
@novusnota novusnota added the priority: highest What should be done first and foremost label Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working or doesn't seem right priority: highest What should be done first and foremost
Projects
None yet
Development

No branches or pull requests

1 participant