amber mailing lists traffic control

Maurizio Cimadamore maurizio.cimadamore at
Fri Mar 24 13:56:42 UTC 2017

one further organizational announcement - as amber is composed by 
several branches, I suggest that, when sending an email _to any of the 
amber lists_ to discuss a given topic (regardless of whether the email 
is related to the code or not), the branch name is used as an header for 
the email subject, using the following pattern:

[<branch name>]: <mail subject>

As we have three branches now, I recommend the following headers are used:

* enhanced enums (JEP 301) -> [enhanced-enums]
* lambda leftovers (JEP 302) -> [lambda-leftovers]
* local variable type inference (JEP 286) -> [lvti]


[lvti]: problem when building repo

This should help in keeping things under control. Of course it's not an 
hard rule, and should you feel that your email doesn't fit any of the 
specific sub-projects, feel free to omit the header.

One last note - currently the only way to try out the branches is to 
build them. We don't have binary snapshots for amber, but we're working 
on a solution. Should this situation change we will let you know.


More information about the amber-spec-experts mailing list