You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/site/content/extra/governance.mdx
+8-8
Original file line number
Diff line number
Diff line change
@@ -1,37 +1,37 @@
1
1
---
2
2
title: Governance
3
-
description: Turbo by Vercel is the next-generation build system for the web.
3
+
description: Turborepo by Vercel is the next-generation build system for the web.
4
4
---
5
5
6
6
- Turborepo was created by the team at [Vercel](https://vercel.com) in 2020.
7
7
- Turbopack was created by the team at [Vercel](https://vercel.com) in 2022.
8
8
9
-
The research and development of Turbo is led by the core team working full-time at Vercel. Turbo is a collaborative open-source effort to build tools for web developers.
9
+
The research and development of Turborepo is led by the core team working full-time at Vercel. Turborepo is a collaborative open-source effort to build tools for web developers.
10
10
11
11
## Teams
12
12
13
-
**Core Team**: Turborepo and Turbopack teams at [Vercel](https://vercel.com) manage the direction of Turbo and leadership of the project.
13
+
**Core Team**: Turborepo and Turbopack teams at [Vercel](https://vercel.com) manage the direction of Turborepo and leadership of the project.
14
14
15
15
**Documentation**: DevRel teams at [Vercel](https://vercel.com) manage documentation and learning platforms.
16
16
17
17
## Roadmap and RFC Process
18
18
19
-
Large architecture decisions and features start as a [Request for Comments (RFC)](https://github.com/vercel/turbo/discussions/categories/rfc) inside GitHub Discussions. The entire Turbo community is invited to be involved in the process and discuss the tradeoffs of proposed work.
19
+
Large architecture decisions and features start as a [Request for Comments (RFC)](https://github.com/vercel/turborepo/discussions/categories/rfc) inside GitHub Discussions. The entire Turborepo community is invited to be involved in the process and discuss the tradeoffs of proposed work.
20
20
21
21
This process is essential to ensure features are built together with the community and our collaborators. More minor changes including bug fixes and documentation improvements are still implemented through GitHub pull requests. However, for larger initiatives, we believe it's essential to follow the RFC process.
22
22
23
23
## Stability and release phases
24
24
25
25
-**Experimental**: Experimental features lack essential capabilities required to be ready for stability. The feature is considered to be under active development and is being built to transition into Beta.
26
-
-**Beta**: Beta means the feature does not yet meet our quality standards for a stable release. There is also usually a need for more information or feedback from Turbo developers to validate this feature works as expected in a variety of environments.
26
+
-**Beta**: Beta means the feature does not yet meet our quality standards for a stable release. There is also usually a need for more information or feedback from Turborepo developers to validate this feature works as expected in a variety of environments.
27
27
-**Stable**: When the features reach stability, it is considered ready for use in production. APIs marked as stable will only change in a backward-compatible way unless there is a major release.
28
28
-**Deprecated**: A feature is in the process of being removed. Deprecated features include documentation for existing users with the next steps and information on when to expect the feature to be removed.
29
29
30
-
## Turbo Support
30
+
## Turborepo Support
31
31
32
-
For individual developers looking for free support on their Turbo repositories, they can ask questions in [GitHub Discussions](https://github.com/vercel/turbo/discussions) or in [Vercel Community's `#turborepo` tag](https://vercel.community/tag/turborepo).
32
+
For individual developers looking for free support on their Turborepo repositories, they can ask questions in [GitHub Discussions](https://github.com/vercel/turborepo/discussions) or in [Vercel Community's `#turborepo` tag](https://vercel.community/tag/turborepo).
33
33
34
-
For companies looking for paid support on their Turbo repositories, they can [contact the Turbo team at Vercel](https://vercel.com/contact) for more information.
34
+
For companies looking for paid support on their Turborepo repositories, they can [contact the Turborepo team at Vercel](https://vercel.com/contact) for more information.
Copy file name to clipboardexpand all lines: docs/site/content/repo-docs/reference/scan.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ Enable faster tooling for your Turborepo locally with one, interactive command.
8
8
You'll be taken through a short series of steps to enable the fastest settings for your Turborepo. These optimizations include:
9
9
10
10
-**Git FS Monitor**: `turbo` leans on Git to do file change discovery. Since we have to wait for `git` to tell us about changes, we can use [Git's built-in filesystem monitor](https://git-scm.com/docs/git-fsmonitor--daemon) to get those notifications sooner.
11
-
-**Turbo Daemon**: Turborepo's daemon optimistically understands your repository in the background. By doing shared, common work that `turbo` will need to do when running tasks beforehand, `turbo` will run your tasks faster.
11
+
-**Turborepo Daemon**: Turborepo's daemon optimistically understands your repository in the background. By doing shared, common work that `turbo` will need to do when running tasks beforehand, `turbo` will run your tasks faster.
12
12
-**Remote Caching**: While Turborepo can cache your work locally, it can also share a cache across all of your machines. Enabling [Remote Caching](/repo/docs/core-concepts/remote-caching) makes your caching **multiplayer**, ensuring that you, your teammates, and your CI machines, never do the same work twice.
13
13
-**Check `turbo` version**: We're always working towards making `turbo` better. To ensure you are using the latest version of Turborepo, we'll check your version and remind you to install `latest` if you aren't using it yet.
0 commit comments