Re: [omr-dev] GitHub Label Taxonomy?

["Filip Jeremic" <fjeremic@xxxxxxxxxx>]

Good idea, we need to start tagging the
issues. I suggest to use "Compiler" rather than "JIT"
so as to not set precedents on OMR compiler technology.

- Filip




From:      
 Leonardo <leob@xxxxxxxxxxxxxxxxxx>
To:      
 omr developer discussions
<omr-dev@xxxxxxxxxxx>
Date:      
 09/28/2016 02:39 PM
Subject:    
   Re: [omr-dev]
GitHub Label Taxonomy?
Sent by:    
   omr-dev-bounces@xxxxxxxxxxx

---

I like this idea.

Perhaps a better word for "Feature" could be "Improvement"?
In my head, "Feautre" is too specific to accommodate things like
architectural changes.

-- 
Leonardo


On 28/09/16 02:20 PM, Matthew Gaudet wrote:
> With Issues being used more and more, I'm proposing we create a set
of
> labels to help us manage our issues. Philosophically, I think we should
> favour simplicity over complexity, so it's important that not too
many
> different labels get created.
>
> My first draft set of labels would be as follows:
>
> Types:
>
> 1. Bug
> 2. Feature
> 3. Docs
>
> Components:
>
> 1. GC
> 2. Port
> 3. Thread
> 4. JIT
> 5. Test
>
>
> I think an important part of community building would be the final
label
> to be used in conjunction with Bug:
>
> 1. StarterBug -- for Bugs that the originator believes could be tackled
>                  by a
relative beginner.
>
>
> This is of course just a starter draft. I'd love to hear what others
> think.
>
> -- Matthew
>
> _______________________________________________
> omr-dev mailing list
> omr-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/omr-dev
>

_______________________________________________
omr-dev mailing list
omr-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/omr-dev