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

[Meta] Integrations Repository Releases #78

Closed
EricDavisX opened this issue Jun 15, 2020 · 5 comments
Closed

[Meta] Integrations Repository Releases #78

EricDavisX opened this issue Jun 15, 2020 · 5 comments

Comments

@EricDavisX
Copy link
Contributor

This issue is intended to track the process around and the schedule for when Elastic will include Integration package changes into a given release (either experimental or prod).

It is a place-holder for now as the team hashes out some initial thoughts we can post back. We will be interested in any feedback from contributors and consumers.

@EricDavisX EricDavisX changed the title Integrations Repository Releases [Meta] Integrations Repository Releases Jun 15, 2020
@mtojek
Copy link
Contributor

mtojek commented Jun 17, 2020

Not sure what is the intention of this issue. Could you provide a sample information you'd like to see? BTW I think we used to track scope and goals differently.

@EricDavisX
Copy link
Contributor Author

Hi, Marcin - sorry for the delay in reply.

This is intended to host info that is public, is a best-practice for how Elastic Registry can be used, how it can be populated by packages (and relating process) and how Elastic will support its own epr.co registry to serve the Kibanas of the world. Its not intended to tell users / admins what they can't do, but provide a layout for what has worked for us, in our internal package development.

As of this writing, we are waiting on details on a revamp of our process to be sorted out, discussed, implemented and we can post back here. If this isn't the desired forum for hosting this, thats ok by me, I'm just looking to know what we'll do, how we'll do it, how we'll communicate to the outside world and how we'll develop packages and ship them.

We may want to form this into a 'contributing.md' in the correct Packages / Registry (or both) relating repos? And we may want some of it in the formal Elastic Docs for 7.9 (starting from 7.8 and beyond, when Ingest Manager was released). I'd appreciate any help on this, or if I should stand-down and let the core Integrations team take this on? I know @ruflin is on the job and we hope to see some news within a week perhaps.

@ph
Copy link
Contributor

ph commented Jun 29, 2020

@EricDavisX it is an ongoing issues or something we track for a specific releases?

@ruflin
Copy link
Contributor

ruflin commented Jun 30, 2020

I assume this ties into the above? elastic/package-storage#86

@ph
Copy link
Contributor

ph commented Jul 1, 2020

Yes, I think we can close this because of your proposal. cc @EricDavisX

@mtojek mtojek closed this as completed Aug 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants