Skip to content

(Meta) Issue Handling #42

@Mytherin

Description

@Mytherin

Pedro made a good suggestion yesterday regarding the issues. We should have clearer issues that are more broken down into small components rather than big meta issues. This way it is easier for newcomers to pick a small issue and work on it to get started on working on the database. Not so important right now but will become more important after we open source and get more people to work on it.

I propose breaking existing issues into smaller components and labeling them with the components/parts of the system that they relate to.

i.e. ->
Core Components
(Execution)
(Optimizer)
(Parser)
(Planner)
(Storage)
Larger Issues
(Core Design)
(SQL)
Meta Issues
(Documentation)
(Code Quality)
(Meta)
Tools/Extensions
(Shell)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions