Deploying to gh-pages from @ 4f919f6 🚀

search.json

@@ -18,7 +18,7 @@
     "href": "users.html#what-does-r-releases-provide",
     "title": "Users",
     "section": "What does R-releases provide?",
-    "text": "What does R-releases provide?\n\n\n\n\n\n\n1. A home for non-CRAN packages\n\n\n\n\n\nMany R packages do not belong on CRAN. In particular, packages containing compiled code may require toolchains or binary downloads that fall outside of CRAN policy.\nBy contributing a package to R-releases, you may conveniently install the latest released versions of all these packages from a single repository location.\n\n\n\n\n\n\n\n\n\n2. A guarantee of package availability\n\n\n\n\n\nR-releases works seamlessly alongside CRAN. By prioritizing CRAN in the settings above, you can continue getting packages from CRAN, only using R-releases as a fall-back.\nA package may become unavailable on CRAN at any time due to its strict archival policy.\n\nSometimes due to the archival of a dependency, and outside the maintainer’s direct control.\nSituations can be temporary, but may take an extended time to resolve.\n\nBy contributing a package that you rely on, you can ensure it always remains available for your critical workflows.\n\n\n\n\n\n\n\n\n\n3. A distribution channel direct from maintainers\n\n\n\n\n\nMaintainers may use R-releases as a faster release channel, especially for packages under intensive development.\nCRAN is first and foremost an archival network, and its policy restricts the frequency of package updates. R-releases allows maintainers to push critical updates or bug fixes directly to users.\nIf a package maintainer recommends that you install a package from R-releases, please prioritize R-releases in front of CRAN in the repository settings above."
+    "text": "What does R-releases provide?\n\n\n\n\n\n\n1. A home for non-CRAN packages\n\n\n\n\n\nMany R packages do not belong on CRAN. In particular, packages containing compiled code may require toolchains or binary downloads that fall outside of CRAN policy.\nBy contributing a package to R-releases, you may conveniently install the latest released versions of all these packages from a single repository location.\n\n\n\n\n\n\n\n\n\n2. A guarantee of package availability\n\n\n\n\n\nR-releases works seamlessly alongside CRAN. By prioritizing CRAN in the settings above, you can continue to get packages from CRAN, only using R-releases as a fall-back.\nA package may become unavailable on CRAN at any time due to its strict archival policy.\n\nSometimes due to the archival of a dependency, and outside the maintainer’s direct control.\nSituations can be temporary, but may take an extended time to resolve.\n\nBy contributing a package that you rely on, you can ensure it always remains available for your critical workflows.\n\n\n\n\n\n\n\n\n\n3. A distribution channel direct from maintainers\n\n\n\n\n\nMaintainers may use R-releases as a faster release channel, especially for packages under intensive development.\nCRAN is first and foremost an archival network, and its policy restricts the frequency of package updates. R-releases allows maintainers to push critical updates or bug fixes directly to users.\nIf a package maintainer recommends that you install a package from R-releases, please prioritize R-releases in front of CRAN in the repository settings above."
   },
   {
     "objectID": "index.html",

sitemap.xml

@@ -2,26 +2,26 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
     <loc>https://r-releases.github.io/users.html</loc>
-    <lastmod>2024-03-14T11:28:38.976Z</lastmod>
+    <lastmod>2024-03-14T11:53:18.225Z</lastmod>
   </url>
   <url>
     <loc>https://r-releases.github.io/index.html</loc>
-    <lastmod>2024-03-14T11:28:38.972Z</lastmod>
+    <lastmod>2024-03-14T11:53:18.221Z</lastmod>
   </url>
   <url>
     <loc>https://r-releases.github.io/conduct.html</loc>
-    <lastmod>2024-03-14T11:28:38.972Z</lastmod>
+    <lastmod>2024-03-14T11:53:18.221Z</lastmod>
   </url>
   <url>
     <loc>https://r-releases.github.io/about.html</loc>
-    <lastmod>2024-03-14T11:28:38.972Z</lastmod>
+    <lastmod>2024-03-14T11:53:18.221Z</lastmod>
   </url>
   <url>
     <loc>https://r-releases.github.io/contributors.html</loc>
-    <lastmod>2024-03-14T11:28:38.972Z</lastmod>
+    <lastmod>2024-03-14T11:53:18.221Z</lastmod>
   </url>
   <url>
     <loc>https://r-releases.github.io/review.html</loc>
-    <lastmod>2024-03-14T11:28:38.976Z</lastmod>
+    <lastmod>2024-03-14T11:53:18.225Z</lastmod>
   </url>
 </urlset>

users.html

@@ -245,7 +245,7 @@ <h2 class="anchored" data-anchor-id="what-does-r-releases-provide">What does R-r
 </div>
 <div id="callout-2" class="callout-2-contents callout-collapse collapse">
 <div class="callout-body-container callout-body">
-<p>R-releases works seamlessly alongside CRAN. By prioritizing CRAN in the settings above, you can continue getting packages from CRAN, only using R-releases as a fall-back.</p>
+<p>R-releases works seamlessly alongside CRAN. By prioritizing CRAN in the settings above, you can continue to get packages from CRAN, only using R-releases as a fall-back.</p>
 <p>A package may become unavailable on CRAN at any time due to its strict archival policy.</p>
 <ul>
 <li>Sometimes due to the archival of a dependency, and outside the maintainer’s direct control.</li>