Hello team, we have discussed this morning to discuss the two demos we need for presenting Wayang at the BOSS workshop, co-located with the biggest database conference (VLDB) and ApacheCon. The demo for BOSS is almost ready (2days max) and the demo for ApacheCon will be ready by mid-September. For the latter, we basically need to create a 2/3mins video showing how Wayang can run data analytics on IoT data.
Regarding the first release of Wayang, we decided to get the first release done once the demos are ready so that we have the system well tested and documented. We will discuss this again with Alex this afternoon: perhaps, we might have the first release sooner. Best, Jorge On Wed, Aug 11, 2021 at 2:58 AM jorge Arnulfo Quiané Ruiz < [email protected]> wrote: > Hey team, > > Bertty, Rodrigo and I are meeting tomorrow at 10am Berlin time to discuss > our two demos as well as the plan for the first release. We will summarize > our discussion in an email here for you! > > Best, > Jorge > > On Tue, Aug 10, 2021 at 10:38 AM Alexander Alten <[email protected]> wrote: > >> Hey team, >> >> Fully agree with Chris, option 2 it is :) >> >> Cheers, >> —Alex >> >> > On 10. Aug 2021, at 10:30, Christofer Dutz <[email protected]> >> wrote: >> > >> > Hi Folks, >> > >> > just a suggestion ... if you want to start a release ... I would >> suggest to do one of these two: >> > >> > - Announce that a release candidate will be created in a week or so and >> to ask everyone to do an audit of the codebase prior tot hat >> > - Cut a release-branch and announce a code-freeze phase of a week or so >> on that branch and ask everyone to do an audit of the codebase there ... in >> this code-freeze phase only fixes to release-relevant things should be >> allowed (No new features or regular development) >> > >> > (I would opt for option 2 - release branch with code stabilization >> phase) >> > >> > Reasoning behind this: >> > At least I will be doing some thorough checks on the release ... >> especially for the first releases, the chance is high, that there will be >> problems and this could cause a lot of release candidates. If we spot >> things early, this is a lot less work for the Release Manager. >> > >> > So if you want to avoid doing too many extra loops, do your checks >> first and produce the official release artifact after a stabilization phase. >> > >> > Chris >> > >> > >> > -----Ursprüngliche Nachricht----- >> > Von: Alexander Alten <[email protected]> >> > Gesendet: Dienstag, 10. August 2021 08:48 >> > An: [email protected] >> > Betreff: release >> > >> > Hey dev community, >> > >> > I’d suggest we start to draft our first release, I know we might miss >> something in the documentation, but I also believe the docs are a living >> space. Means we can update them more agile. >> > >> > What do you think? >> > >> > Cheers, >> > —Alex >> > >> > — >> > PPMC Apache Wayang >> > [email protected] >> >>
