Announcing: valhalla-spec-experts group
brian.goetz at oracle.com
Mon Dec 14 22:28:47 UTC 2015
Eventually, yes; there's no reason not to have these, except for the
administrative overhead of setting them up. But I didn't want to delay
getting the discussions going in a more transparent manner over
administrivia, so these will come later, and of course I'll announce
them here when they do.
On 12/14/2015 5:24 PM, Ali Ebrahimi wrote:
> Hi Brian,
> Wouldn't we have valhalla-spec-(observers/comments)?
> Best Regards,
> Ali Ebrahimi
> On Mon, Dec 14, 2015 at 11:37 PM, Brian Goetz <brian.goetz at oracle.com
> <mailto:brian.goetz at oracle.com>> wrote:
> It's time to take the next step in Valhalla's evolution.
> Accordingly, I've created the valhalla-spec-experts list, which
> will be the precursor to an eventual JCP Expert Group, and will
> operate under the JCP-friendly ToU. This list is publicly
> archived in the obvious place, and the initial membership includes
> both corporate participation (Oracle, IBM, Red Hat, Jetbrains,
> Google) and individuals from the OpenJDK community.
> As was the case when we formed the Lambda experts list, the role
> of valhalla-dev should now revert to its intended purpose, which
> is to discuss the *implementation* of Valhalla in OpenJDK.
> Examples of appropriate discussion topics for valhalla-dev include:
> - Bug reports
> - Code review comments
> - Test cases
> - Build or porting problems
> - Migration experiences for your own code
> What we are trying to avoid is: having design discussions play out
> concurrently in multiple places with differing sets of players.
> So please, we ask that you exercise restraint in commenting on
> active EG discussions -- as design decisions start to converge,
> we'll announce them here, and of course the primary place for
> implementation will remain the valhalla repositories.
> Please remember that EG discussions often happen at a different
> pace than in other open-source projects. Days can go by without a
> response, but this doesn't mean that the EG is not thinking about
> it, doesn't care, or is "stumped". Often it simply means the EG
> members are working privately (or with their teams) to figure out
> what their position is, and will respond when they've thought
> about it more. So, please let those discussions play out.
More information about the valhalla-dev