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

Add "installing from a nightly release" guide to install section #1192

Closed
samodell opened this issue Apr 17, 2019 · 12 comments
Closed

Add "installing from a nightly release" guide to install section #1192

samodell opened this issue Apr 17, 2019 · 12 comments
Assignees

Comments

@samodell
Copy link
Contributor

Describe the change you'd like to see
The install section should include information about installing from the nightly component releases, not just the latest numbered release

@samodell samodell added triage/needs-eng-input Engineering input is requested kind/good-first-issue Denotes an issue ready for a new contributor. priority/high kind/install labels Apr 17, 2019
@samodell samodell added this to the Backlog milestone Sep 3, 2019
@knative-housekeeping-robot

Issues go stale after 90 days of inactivity.
Mark the issue as fresh by adding the comment /remove-lifecycle stale.
Stale issues rot after an additional 30 days of inactivity and eventually close.
If this issue is safe to close now please do so by adding the comment /close.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/lifecycle stale

@knative-prow-robot knative-prow-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 3, 2019
@abrennan89
Copy link
Contributor

@samodell this one probably makes sense to do once we have separate install guides for Serving and Eventing.
Maybe add this as a note for #1922 and #1923 so that this comment doesn't get lost if the issue goes stale before these get separated?

I'll add the details about nightly builds to the CLI install docs.

@samodell
Copy link
Contributor Author

/remove-lifecycle stale

@knative-prow-robot knative-prow-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 11, 2019
@samodell samodell added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed triage/needs-eng-input Engineering input is requested labels Jan 16, 2020
@abrennan89 abrennan89 modified the milestones: Backlog, Icebox May 15, 2020
@abrennan89 abrennan89 modified the milestones: Icebox, Backlog Jan 25, 2021
@abrennan89 abrennan89 added triage/needs-eng-input Engineering input is requested and removed lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/high labels Mar 15, 2021
@abrennan89
Copy link
Contributor

@omerbensaadon do you want to take a crack at this one or add it for in the DUX group?

@omerbensaadon
Copy link

I'll throw this on the DUX agenda 👍🏼

@abrennan89
Copy link
Contributor

@evankanderson do you know how to do this? This issue has been open forever so I'd like to see us close it, whether that's because we don't intend to doc this or because someone can give me the info 😄

@evankanderson
Copy link
Member

I need to look up where the nightly artifacts are stored. Let me do that...

/assign

@abrennan89 abrennan89 removed the kind/good-first-issue Denotes an issue ready for a new contributor. label Jul 16, 2021
@abrennan89
Copy link
Contributor

Ehhh I just noticed the docs at https://knative.dev/development/admin/install/serving/install-serving-with-yaml/#install-the-knative-serving-component actually use a URL that points to knative-nightly - have we then been telling people to install the nightly version this whole time, and if so should we not be doing that and be pointing to a stable, released version instead @evankanderson ?

@julz
Copy link
Member

julz commented Jul 16, 2021

the development/ docs (i.e. pre-release from the drop-down) link to the nightly release (since the development docs might refer to features that aren't in the latest stable version), the docs/ docs (v0.24 in the dropdown) link to the current stable release (e.g. https://knative.dev/docs/admin/install/serving/install-serving-with-yaml/#install-the-knative-serving-component).

@julz
Copy link
Member

julz commented Jul 16, 2021

having said that I do still think an explicit "How to install the nightly release" might be useful in docs/, rather than requiring people to know to flip the dropdown to pre-release, iyswim

@evankanderson
Copy link
Member

It's possible that kn quickstart might resolve this, but I think it's worth a note somewhere about the availability of the GCS manifests, as that that allows automation to avoid the GitHub API rate limits, which are pretty tight.

@abrennan89 abrennan89 removed this from To do in [EPIC] Clean up cruft Aug 18, 2021
@abrennan89 abrennan89 removed this from the Icebox milestone Aug 18, 2021
@abrennan89 abrennan89 added this to Needs triage in Issue triage via automation Aug 18, 2021
@abrennan89
Copy link
Contributor

Closing this since the issue is 2 years old and these docs technically are available on the development version of the site. We can revisit if this or something similar is requested by users in the future.

Issue triage automation moved this from Needs triage to Closed Sep 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

8 participants