> > 1) LSP4J is contributing 0.8.1 not 0.9.0 as listed in the > participation page >
Updated. Thanks for checking. > 2) Does the new tooling that understands npm also understand yarn? I have > an IP log to submit for CDT and part of it uses yarn to build. It doesn't directly understand yarnm, but it does understand pURL. But it currently only runs on my workstation (I'm pushing to have a first generally usable version of the tool available by the end of the year). I just ran it against https://github.com/eclipse-cdt/cdt-vscode.git and it found a few things for which it can't resolve the licenses (so we'll have to resolve them and add that information to the database). This will be a good first test of attaching dependency lists to IP Log CQs. Can you submit the IP Log sometime soon (early this week would be ideal) and attach the result of running "yarn list" in all the places that you use yarn? FWIW, I'm capturing requirements for the process on Bug 553649 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=553649>. Wayne On Fri, Nov 29, 2019 at 5:21 PM Jonah Graham <jo...@kichwacoders.com> wrote: > Hi Wayne, > > 1) LSP4J is contributing 0.8.1 not 0.9.0 as listed in the > participation page > > 2) Does the new tooling that understands npm also understand yarn? I have > an IP log to submit for CDT and part of it uses yarn to build. > > Thanks > Jonah > > ~~~ > Jonah Graham > Kichwa Coders > www.kichwacoders.com > > > On Fri, 29 Nov 2019 at 15:37, Wayne Beaton < > wayne.bea...@eclipse-foundation.org> wrote: > >> Greetings folks! >> >> I've created the 2019-12 Participation page >> <https://projects.eclipse.org/releases/2019-12> using the information >> that I could find. Let me know if anything is incorrect. >> >> By way of reminder, if you are including new bits in this edition of the >> simultaneous release, you'll need a release record that indicates the >> version that you are contribution. There's more help in the wiki >> <https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early> >> . >> >> If you have not engaged in a release review >> <https://www.eclipse.org/projects/handbook/#release-review> in the last >> year, then you will need to engage in that process ASAP. >> >> Note that, per the IP Policy updates approved by the Eclipse Board of >> Directors in October 2019, piggyback CQs are no longer required. I owe you >> all a much longer discussion about these changes (which are more extensive >> than just not needing piggybacks) which I promise to provide before the end >> of the year. I've started here >> <https://waynebeaton.wordpress.com/2019/11/13/reviewing-third-party-content/> >> . >> >> Note also that, even if you are contributing new bits, but do not >> require a release review because you've done one in the last year already, >> the intellectual property contained (and referenced by) your release must >> be fully vetted by the IP due diligence process. >> >> The simultaneous release participation rules require that projects >> consume third party content via Eclipse Orbit, so this shouldn't be a >> problem for most of you. For those projects that consume third party >> content from outside of Orbit (e.g., those projects that consume NPM >> content), or are otherwise unsure of due diligence status of any of their >> content, you can submit an IP Log and I'll take a look. >> >> Wayne >> -- >> >> Wayne Beaton >> >> Director of Open Source Projects | Eclipse Foundation, Inc. >> _______________________________________________ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Wayne Beaton Director of Open Source Projects | Eclipse Foundation, Inc.
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
