2019-12-10 Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window) PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2019-09-04 Onboarding call 2019-09-17 Contributor call 2019-10-01 Contributor call 2019-10-15 Contributor Call 2019-10-29 Contributor Call 2019-11-12 Contributor Call 2019-11-26 Contributor Call 2019-12-10 Contributor Call 2020 Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2019-12-10 Contributor Call More actions 2019-12-10 Contributor Call Danno Ferrin Owned by Danno Ferrin Last updated: Dec 10, 2019 Meeting Video: dummyfile.txt Housekeeping General Announcements Release Updates 1.3.6 Discussed 1.4 beta release proposal Beta vs rc? HLP Release Taxonomy Branches for 1.3 maintenance if needed and 1.4 for 1.4.0 Master for 1.3.7, 1.4 beta, and 1.4.1 rc 13 Feb 2020, full release on 27 Feb 2020 1.3.8 becomes 1.4.0-beta 15 Jan 2020 Beta 2 if needed on 29 Jan 1.4-RC on 13 Feb 2020 1.40 targeted at 27 Feb 2020 Build version becomes 1.4.0-beta-SNAPSHOT right after 1.3.7 release Work Updates Change Log Only include PRs that have useful changes rather than a line for each PR Either Add a CHANGELOG section to each PR Use a wiki page. Can we keep the changelog in the wiki and not keep it in the codebase? Why not have updating the change log as part of the PR? There will always be merge conflicts Whatever change happens will require an adjustment of habits. Proposal: Make an actual change to the PR as part of the log Standalone commit Or as part of the changes We will try this for the next release or so. Someone will need to review and ensure this is being practiced. Add to contributor guidelines  Custom RPC endpoints plugin service Other Business Edward Mack as Maintainer. CI/CD Jenkins is dead. Circle CI for everything. It has the most scope for being faster compared to all other CI systems we have looked at Working on posting build failures to rocket chat All infrastructure and tooling is on HLP owned/operated Zero servers owned by ConsenSys Open Forum Next Meeting - 7 Jan 2020 - EMEA/AMER time Action Items  - Madeline to update contributor guidelines to reflect Change Log and communicate. , multiple selections available,meeting-notes {"serverDuration": 38, "requestCorrelationId": "0e890dfa82624ff0b7c3baf2595e3877"}