The GX issues board is a GitHub Project that we created in order to create transparency around which GX GitHub issues are GX-supported, and which are community-supported, as well as to serve as a space for GX engineers to track their progress in the open.
Types of issues
For any issues that comes in, they will fall under one of the following types of issues:
- Community-supported
- GX-supported
- Not-supported
What an issue is labeled will align with our integration and support policy, which outlines what is GX-supported, community-supported, and not supported.
GX-supported issues
If an issue is GX-supported, this means it is related to a part of the code-base that is tested and actively maintained with new GX Core or GX Cloud releases. The steps we will take for these issues are as follows:
We will work to reproduce the issue. This may involve us requesting additional information from the person who submitted the issue.
If the issue can be reproduced on our end, it will be prioritized by engineering.
You can find GX-supported issues on the Issues by Status tab of the GX Issues board; the Reported Bugs tab shows an additional view with just bugs. Any issues that do not have the community-supported or not-supported label can be assumed to be GX-supported.
Community-supported issues
If an issue is labeled as community-supported, it is related to a part of the code-base that is not tested and actively maintained with new GX Core or GX Cloud releases, and it is up to the community to ensure ongoing maintenance.
You can find community-supported issues on the community-supported tab of the GX issues board.
Process for contributing
If there is an issue that you’re planning to tackle, simply comment on an issue that you’re starting to work on a fix.
You can also optionally post in the #contributing channel in the GX slack that you’re taking on that issue, especially if you’re interested in teaming up with others who may be thinking about the same issue.
Not-supported
If an issue is labeled as not-supported, it is something that we at GX will not be maintaining, and we will not support PRs or contributions from the community on the topic. See our integration and support policy for details on what is and is not supported.
0.x issues
Moving forward, we will focus our resources on supporting and improving version 1.0 and beyond. If you find that an issue you previously reported still exists in version 1.0, we encourage you to resubmit it against the new version.
For help migrating to GX Core, check out the GX V0 to V1 Migration Guide.
Submitting an issue
Submit issues to the Great Expectations project here.
We understand that when you encounter an issue while coding, you want quick and efficient resolution.
To help us help you better, we request that you include the following information in your questions:
-
Environment: Please let us know the environment in which you are working in.
- Operating system:
- Version numbers:
- Programming language:
-
Problem Statement:
- I was trying to do the following:
- Instead, this is happening:
-
Reproducing the issue: Details necessary to enable us to reproduce the issue and provide a quick resolution. E.g.: What commands or code did you run and/or what actions did you take that led to the issue?
Steps to reproduce the behavior could look something like the following:- I ran this command or piece of code ‘…’
- OR I clicked on ‘…’ and scrolled down to '…’
- I now see this error or stack trace ‘…’
-
Additional information: Provide us with any other additional information that could be useful in solving your issue.
By providing us with this information, you help us provide you with a quicker and more efficient resolution. We understand that time is of the essence when it comes to coding, and we want to ensure that we can resolve your issue as quickly as possible.