On 5/20/16 4:45 PM, Jason Greene wrote:
Hello Everyone,
I’d like to cut a 10.1 fairly soon, preferably in the next 2-3 weeks. My thinking is to
take everything that is not explicitly tagged as 11.x
Remember that fairly few people can add github labels, so the present
set of "11.x" labels really amounts to a couple peoples's tagging,
mostly me semi-randomly looking at stuff I expect. So it's probably a
good idea for people, component leads in particular, to mark ASAP ones
that they don't think should be in 10.1. Probably changing the title to
include "11.x" or similar is easiest.
and merge it ASAP. Really this should just be anything that doesn’t
add instability, or introduces a half-finished API that we then have to support (the
obvious exception is experimental capabilities that we denote as such). This is a bit of a
departure from what I was suggesting earlier, where we we would cherry-pick major items
into a separate branch, so if you have any concerns now is the time to raise them.
This release would be a good opportunity to include features that are ready to go
(suitable for a final release in 2-3 weeks) but didn’t make 10.0 (I have a feeling Sanne
has been itching for some updates to search!). If you have something then send a PR
(noting that you want it in 10.1) or raise your figurative hand :)..
Thoughts?
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat