Resending with the address that is subscribed to the list, as i didn’t notice my MUA using the wrong one.
Begin forwarded message: > From: "Andrew Yourtchenko (ayourtch)" <ayour...@cisco.com> > Date: 17 June 2020 at 20:47:51 CEST > To: vpp-dev <vpp-dev@lists.fd.io> > Cc: Ole Troan <otr...@employees.org>, "Vratko Polak -X (vrpolak - PANTHEON > TECH SRO at Cisco)" <vrpo...@cisco.com>, Dave Wallace <dwallac...@gmail.com>, > "Mohsin Kazmi (sykazmi)" <syka...@cisco.com>, "Benoit Ganne (bganne)" > <bga...@cisco.com>, Florin Coras <fcoras.li...@gmail.com>, "Aloys Augustin > (aloaugus)" <aloau...@cisco.com> > Subject: VPP API CRC compatibility check process in checkstyle merged and > active > > > Hi all, > > the API compatibility process check has been just merged today and is now > active: > > https://gerrit.fd.io/r/c/ci-management/+/27414 > > This means that from now on all the gerrit changes on master branch will be > checked to satisfy the production APIs compatibility guarantees. > > If that check fails, in the Checkstyle job logs you will find a invitation to > get in touch with me and the reference to the process page: > > https://wiki.fd.io/view/VPP/ApiChangeProcess > > If you are working with an API - please have a read and let me know if > anything there is outrageous. I think I incorporated all the feedback. > > I may have missed something or worded something unclear - happy to tweak it > if you suggest improvements - note the process page is marked as “work in > progress”. > > I expect we might need to tweak it. This will need communication. For this > reason I will also get a notification so I know to be ready and have the > context of the discussion. (Also to see if the wheels fall off at any point > accidentally - ping me if I don’t ping you). > > The core vision of the process is not expected to change, though: > > “if you only use production non-deprecated APIs in the release X, the (one) > upgrade to release X+1 is possible without client code changes”. > > If after that upgrade you discover which APIs are deprecated, and get rid of > their use you gain another “hassle-free” upgrade to X+2, etc. > > This also means (assuming there are no bugs in the process or checker), and > unless some of the (supposedly unused but you use them and didn’t speak up) > API messages being reclassified to “in-progress”, you can already start > testing the current master with your northbound code “as if” it were the > 20.09 API-wise, as we have only two incompatible messages since 20.05: > > > > > > > > ubuntu@vpp-dev:~/vpp$ ./extras/scripts/crcchecker.py --git-revision v20.05 > added: gtpu_tunnel_update_tteid > added: gtpu_tunnel_update_tteid_reply > added: map_domains_get_reply > added: map_domains_get > modified: ** gtpu_tunnel_details > modified: ** gtpu_add_del_tunnel > ubuntu@vpp-dev:~/vpp$ > > I would highly encourage everyone to test this process on a > 20.05<->Current_master transition and let me know what the results are, so > we can iron out the kinks in the process sooner or than later. > > If we are rigorous with this process, it should enable a few other very > useful optimizations/enhancements further down the line. > > I would like to thank everyone on the CC list: > > - Ole for the great discussions and crcchecker.py heavy lifting > - Vratko and Dave - for the ci-management guidance and orientation > - Mohsin, Benoit and Florin - sanity check, process tuning and feedback. > - Aloys - for bearing with my initial crazy variants of compatible API > management ;-) (Metaprogramming by sed FTW! ;-) > > Thanks! > > --a > (Your friendly YY.MM release manager :-)
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16750): https://lists.fd.io/g/vpp-dev/message/16750 Mute This Topic: https://lists.fd.io/mt/74956323/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
