[jbosstools-dev] News from the Eclipse Planning Council: Neon.1a respin next week, JDK 9 delayed to July 2017, Type A licensing concerns

[Nick Boldt]

Marian,

David had said yes to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=503305. Go vote for the
bug and nag the PMC to get this fixed, built, released ASAP.

https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg02654.html

On Wed, Oct 5, 2016 at 3:46 PM, Nick Boldt <nboldt at redhat.com> wrote:
> I've asked the PC. We'll see what David says.
>
> https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/
>
> On Wed, Oct 5, 2016 at 3:11 PM, Marian Labuda <mlabuda at redhat.com> wrote:
>> Hey Nick,
>>
>> do you think it would be possible to include also
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=503305 in respin? They fixed
>> the issue only for master (Oxygen) and left Neon intact with fix. I spotted
>> that issue in RedDeer where some of tests started failing and the reason was
>> that issue. Basically its easy to include bcs. only the same patch has to be
>> merged to a different branch.
>>
>> Cheers
>> Marian
>>
>> On Wed, Oct 5, 2016 at 7:03 PM, Nick Boldt <nboldt at redhat.com> wrote:
>>>
>>> On today's Eclipse Planning Council call, a number of big things were
>>> discussed:
>>>
>>> * A Neon.1a respin is coming next week due to MPC/git blocker bug:
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=501000
>>>
>>> * JDK 9 is delayed again... now scheduled for July 2017. So there will
>>> be some sort of Oxygen.0a release in July to accommodate all the JDK9
>>> support problems that come up. Oxygen.1 will still be in September
>>> 2017, as scheduled.
>>>
>>> * There was also much discussion around the new Type A (only the
>>> license is checked) vs. Type B (old school full due diligence, with
>>> code provenance checked too) licensing. Decision was to only include
>>> type B stuff in release train for now, and wait for projects to
>>> complain they should be included, or perform more due diligence to be
>>> upgraded to Type B. Including Type A stuff opens a lot of trickle-down
>>> problems that no one wants to deal with unless we have to, such as
>>> "will end users still be allowed by their employer to use Eclipse, if
>>> there's no longer a guarantee of provenance check in the bundles?".
>>> More: https://bugs.eclipse.org/bugs/show_bug.cgi?id=501014
>>>
>>> ===
>>>
>>> Full agenda & David's minutes, once he adds them, will be here:
>>> https://wiki.eclipse.org/Planning_Council/October_05_2016
>>>
>>> --
>>> Nick Boldt :: JBoss by Red Hat
>>> Productization Lead :: JBoss Tools & Dev Studio
>>> http://nick.divbyzero.com
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>
>
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com



-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com