[llvm-dev] Policy on support tiers

[Renato Golin via llvm-dev]

Examples of tier 2 breaking 1 are when a change in its code need & warrant
a change in common apis (in tier 1), and those changes break unrelated tier
1 code.

I agree it's not super well defined, but I really think we shouldn't try to
list what is in/out of each tier and I'm hoping people can help me define
the scope of each.

Questions like yours are super helpful to do just that.

Thanks!
Renato

On Sat, 31 Oct 2020, 02:21 Neil Nelson via llvm-dev, <
llvm-dev at lists.llvm.org> wrote:

> Renato,
>
> By your earlier requirements for tier 1, not seeing how tier 2 could break
> tier 1. If a file was in tier 2, it would not be in tier 1. There would be
> no action in tier 1 on tier 2 files to cause a break.
>
> What this may mean is that those working in tier 2 do not wander into tier
> 1, obscuring that distinction. Or that there may be some confusion about
> what was in tier 1 vs. 2. That in some manner the distinction becomes not
> well defined.
>
> Neil Nelson
> On 10/30/20 6:13 PM, Renato Golin via llvm-dev wrote:
>
> But I wanted to express: "3 can't break 2 can't break 1", and make it
> easier to drop silly scripts or config files if they're no longer valid or
> maintained, more easily than dropping entire build systems.
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201031/5c80b522/attachment.html>