METRON-867: In the event that we graduate, remove incubating from the website and documentation #539
Conversation
… website and documentation
There are some incubator references remaining in the site-book
|
Yes, those are referencing our github repo, which is "incubator-metron". We would have to change those references after we move infrastructure around post-graduation (if it happens). I didn't want to break functionality in the interrim while that happens. |
OK, that makes sense. Spinning up full dev now. |
Am I missing something? I thought we were approved for graduation as of last night. The email seemed pretty clear that we were done with the incubator and that we graduated on 4/19/17. |
Yeah, just waiting for the press release before we make this too public. |
+1. Spun up full dev and verified index is still populating via |
+1, I took a look through the site and didn't see anything wrong and also searched the code a bit for signs of incubation. Do we have tickets for any of the follow-on work mentioned, e.g. the changing the repo references? |
No, no follow-on tickets as of yet. I was planning on looking at it Monday after the press release and formulating a plan and discussing with the community any impact that might have. If anyone wants to take a gander earlier than that and create some JIRAs, I'd not be opposed to that. It doesn't take the VP, just a PMC member to push the buttons, but pretty much anyone in the community can formulate a plan. |
I'm fine with looking at it Monday. I may take a quick look if there's any JIRAs from other projects we can steal as a starting template, but if not we can start running through the graduation guides and creating tickets as needed. |
… website and documentation closes #539
… website and documentation closes apache/metron#539
Contributor Comments
NOTE:
To test this:
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron (Incubating).
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:
For documentation related changes:
Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via
site-book/target/site/index.html
:Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.