-
Notifications
You must be signed in to change notification settings - Fork 54
Triaging
We are using a special Triage kanban board to classify issues considered for near-term and longer-term implementation plans.
We are organising various topical sprints in order to implement a new feature or make a new release. You can find various Kanban boards associated to our topical sprints here.
Actions to perform when triaging an issue:
-
Check whether the issue contains all the information in order to be understandable and actionable by any developer in the team. If not, complete the information.
-
Assign appropriate labels to help classify the topic, community, priority or indicate implementation complexity.
REANA reproducible analysis platform
blog.reana.io | docs.reana.io | forum.reana.io | www.reana.io |
@gitter | @mattermost | @twitter
Introduction
Getting started
- Setting up your system
- Cloning sources
- Using production-like development mode
- Using live-code-reload and debug mode
Issue lifecycle
Understanding code base
Technology tips and tricks
- Tips for Docker
- Tips for Git
- Tips for GitLab
- Tips for Keycloak
- Tips for Kind
- Tips for Kubernetes
- Tips for OpenAPI
- Tips for PostgreSQL
- Tips for Python
- Tips for RabbitMQ
- Tips for SQLAlchemy