search

jenkins-x / enhancements

Repository containing design proposals for Jenkins X enhancements
12 stars 16 forks source link

docs: enhancement proposal for labs, enable rapid innovation while ke… #15

Closed rawlingsj closed 4 years ago

rawlingsj commented 4 years ago

…eping a stable base platform

Signed-off-by: James Rawlings rawlingsj80@gmail.com

salaboy commented 4 years ago

@rawlingsj great stuff.. I really like the idea.. just to clarify, the proposal for labs is generic and not only focused on the jx cli? or is it only for that now?

pmuir commented 4 years ago

In particular I think that the expectation around alpha and beta is correct. Generally it is accepted that once software enters the beta phase the software is feature complete, and that the beta phase is around hardening (fixing bugs, addressing performance & scalability, security review etc.) https://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha

rawlingsj commented 4 years ago

great stuff.. I really like the idea.. just to clarify, the proposal for labs is generic and not only focused on the jx cli? or is it only for that now?

@salaboy yay - glad you like it :) So yes your first assumption is correct, I can improve the proposal to reflect that. Jenkins X as you know is heavily CLI based but we will want to take similar steps to building docker images, quickstarts, buildpacks etc, that use labs features so they don't appear in Jenkins X until feature complete (using the term from Pete's comment above). I'm sure there will be lots we learn as we start out but in general so far people seem to think it's a good approach. We will probably keep tinkering and improving the process as we learn more.

salaboy commented 4 years ago

@rawlingsj great.. I am looking forward to seeing how the community implements and consumes these different streams, as it is a complicated challenge.

ethangj commented 4 years ago

Something I'd like to see clarified is that alpha doesn't necessarily mean the feature will progress to beta, in our definition alpha means it's an experiment that could disappear entirely and users need to be made away that alpha features are not guaranteed to persist.

Beta, in contrast, would be a commitment that we are taking a feature forward and even if it's not ready yet, we are committing to getting the experiment to wide release eventually.

daveconde commented 4 years ago

All looks good to me

mrageh commented 4 years ago

Nice!

hferentschik commented 4 years ago

LGTM

jenkins-x-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x-bot commented 4 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle rotten

rawlingsj commented 4 years ago

Given the updates around Jenkins X and the reversed direction Jenkins X was taking towards OSS described in this issue https://github.com/jenkins-x/jx/issues/7207 - I think we can close this proposal. I will put together another proposal that focuses on building a more collaborative developer open source community.