Ok ... so as I have the "enum" field in there since yesterday ... any objections that I cut a release branch for the build-tools?
Would release the 1.0.0 as soon as possible (No need for announcements and crap like that) Chris Am 25.09.19, 19:26 schrieb "Julian Feinauer" <[email protected]>: Agree so... Let's release : ) Von meinem Mobiltelefon gesendet -------- Ursprüngliche Nachricht -------- Betreff: Re: Next Release / Usage of AB-ETH Driver Von: Christofer Dutz An: [email protected] Cc: The plugin has been working fine for months. Has just been me extending the shared types several times. Chris Holen Sie sich Outlook für Android<https://aka.ms/ghei36> ________________________________ From: Julian Feinauer <[email protected]> Sent: Wednesday, September 25, 2019 1:25:11 PM To: [email protected] <[email protected]> Subject: Re: Next Release / Usage of AB-ETH Driver See my comment under 2... to make it independent oft hat. But if weg et the plugin out oft he door soon then I'm fine : ) Am 25.09.19, 13:17 schrieb "Christofer Dutz" <[email protected]>: We must release the plugin first ... otherwise we'd have SNAPSHOT dependencies in the release. Chris Am 25.09.19, 12:29 schrieb "Julian Feinauer" <[email protected]>: Hi folks, as we are currently starting to use the new AB-ETH Driver in production I would like to have a (official) release with it included. So two questions: 1. Does anybody offend that we just put the stuff out of sandbox as it works and is fine 2. How do we handle the situation that we do not (yet) have a release of the plugin? Straightfotward approach would be to commit the generated sources (and delete them as soon as code-gen plugin works, ofc). What are your thoughts? Julian
