Skip to content

rxweb issue workflow

Ajay Ojha edited this page Nov 29, 2018 · 4 revisions

This page will describe the lifecycle of the issue.

What is an issue?

We have categorized the issue, which will helpful for development/documentation team.

  1. Bug
  2. Docs: Bug

An issue is not:

  1. Docs: Undocumented
  2. Feature Request
  3. Help

Issue Creation

  1. You can log the issue directly from the GitHub repo; if you are on rxweb.io site, then you will find report issue link on the right side of the page.
  2. In the title field, please write a summary of the issue.
  3. In the description field, Add the required details as per the issue category.

Issue Grooming

Within 24 hours, someone from the rxweb framework team should label the issue and directly respond to you. We may ask a few questions to gain a better understanding of the problem. If we do not get a response from you within three days, we may close the issue.

Issue Resolution

If the issue is valid and clearly defined, it will be assigned to rxweb framework team, and development will begin. Within three days, a pull request should be submitted, reviewed, and merged. A rxweb framework team gives a working solution stackblitz link and release the same.

Closing an Issue

Within a week, an issue should be closed for one of three reasons:

  1. The issue was fixed.
  2. The issue was a question or feature request.
  3. The issue was not clear enough to resolve.
Clone this wiki locally