Hi! > Just wanted to start a quick discussion about 3.0.x. We’ve historically > done work on the master and then supported two fixes branches. With 3.2.0 > being voted on now, I’m not sure if we would branch the 3.2.x-fixes branch > immediately or wait a bit (we have historically waited a bit). Are there > major changes forthcoming that would warrant targeting 3.3 sooner? If not, > I think I’d like to stick on master for at least one round of fixes just to > stabilize the 3.2.0 as users migrate. Maybe for JDK 9? But currently I would wait and keep 3.2.x in master...
> In any case, we’ve now supported the 3.0.x series for 2 years, 4 months. > Would it make sense to announce that 3.0.15 will be the final scheduled > release off that branch? Maybe wait one more iteration? We haven’t been > back porting much anyway. I grabbed the “central download stats” from > Nexus for the cxf-core module (pretty much any usage of CXF requires that) > just to get an idea of what is used. The top 10 are: > > 3.0.3 18% > 3.1.11 11% > 3.1.6 10% > 3.1.10 7% > 3.1.12 6% > 3.1.7 5% > 3.1.8 5% > 3.1.5 4% > 3.1.4 4% > 3.0.1 4% > No 2.7.x version within the top 10? I think we should declare 3.0.15 as the last 3.0.x release. We can make an exception if security fixes are necessary. The projects I know either still use 2.x or already migrated to 3.x-latest. Cheers Dennis
