This version (2017/05/27 13:44) is a draft.
Approvals: 0/1

[06:15:11] * ChanServ sets mode: +o purplefox [08:42:15] <cescoffier> Hello purplefox and pmlopes [08:42:22] <cescoffier> just reconnecting…. [09:00:38] <pmlopes> good morning [09:08:10] <cescoffier> pmlopes: did you see the jdbc client build issue [09:08:30] <cescoffier> it is related to vertx-sync. Something missing in vertx-sql-common [09:08:54] <cescoffier> I think I've found it [09:13:30] <cescoffier> purplefox: I've seen you removed the vertx-sync dependency from vertx-sql-common. Any reason ? [09:14:25] <cescoffier> ( purplefox pmlopes - this is the reason why the jdbc client does not built anymore) [09:18:25] <pmlopes> cescoffier, i haven't seen it yet i will have a look [09:18:51] <cescoffier> pmlopes: I've fixed it locally, but it redo something removed by purplefox [09:19:05] <cescoffier> (so I would like to know the reason behind this change) [09:23:08] <purplefox> cescoffier: pmlopes: morning guys [09:23:20] <purplefox> pmlopes: hope you had a good holiday! [09:25:00] <pmlopes> purplefox, yes they were nice, and now to make things more exciting i'm working on a windows 10 machine :P my laptop is back at the repair place somewhere in Germany :) [09:25:45] <pmlopes> bwt the jdbc does not build for me because it does not resolve the sync package from common-sql [09:26:16] <cescoffier> pmlopes: it does not resolve it because it's not generated in common-sql [09:26:50] <purplefox> ah did i forget to remove it from jdbc too? [09:27:31] <cescoffier> purplefox: do you want to remove it or to add it [09:27:47] <purplefox> remove it [09:27:48] <cescoffier> you removed it from sql-common but not from the jdbc client [09:27:49] <cescoffier> ok [09:28:05] <cescoffier> so, I will remove it from JDBC [09:28:42] <pmlopes> ok [09:28:43] <purplefox> it's ok i'm doing it [09:29:31] <cescoffier> jenkins is going to reboot [09:33:36] <purplefox> ok done [09:37:53] <purplefox> pmlopes: ha, windows 10. good luck with that ;) [09:42:19] <pmlopes> purplefox, it if funny you start intellij open the terminal and it does not work, the edge browser works but it does not feel as fast as ms wants us to think with all the publicity they made [09:43:11] <purplefox> pmlopes: apparently vert.x doesn't work on windows 10 (some probably with scripts) /cc cescoffier [09:43:25] <cescoffier> purplefox: ah ah ah [09:43:33] <purplefox> pmlopes: also I've heard there are some serious issues with privacy too [09:43:35] <cescoffier> actually it's kind of interesting [09:43:49] <cescoffier> because it works, I've tested it on 2 different machines using windows 10 [09:44:05] <cescoffier> the guy has a configuration issue. [09:44:26] <purplefox> ok, so that's a relief then [09:45:32] <pmlopes> if there's anything we need to test on win10 let me know, because my laptop will only return next week [09:50:22] <cescoffier> Yes definitely a relief [09:56:50] <cescoffier> purplefox: gonna automate your vertx-sync example [09:57:05] <cescoffier> I will let you know when it's done (on Stomp right now) [10:10:24] <purplefox> cescoffier: pmlopes: hey guys are there any PRs you would like me to review that I've missed? [10:10:51] <purplefox> cescoffier: how about the starter stuff, is that ready for review? [10:11:05] <cescoffier> purplefox: Let's wait Julien [10:11:13] <purplefox> ok sure [10:11:16] <cescoffier> I want to be sure about the integration in vert.x shell first [10:12:05] <cescoffier> the ideas and implementation are there, now it's just a question or organization and check it will work in the vert.x shell context [10:13:11] <purplefox> ok [10:22:04] <purplefox> cescoffier: pmlopes: that reminds me. I think we should do a 3.0.1 maintenance release before too long as we have a few fixed bugs now [10:22:35] <cescoffier> yes, definitely [10:23:00] <cescoffier> how do we handle that, it is per module and we adapt the stack, or do we release the whole stack ? [10:25:45] <purplefox> i assume we release a new version of vertx-stack but only release new versions of components if they have changed [10:26:02] <purplefox> (so the stack might contain some components at 3.0.0, others at 3.0.1 [10:35:54] <cescoffier> purplefox: we should start looking at elligible components [10:50:28] <purplefox> pmlopes: hey paulo, looking at PR for json changes, but it seems to contain the sendfile range changes instead [10:51:33] <purplefox> cescoffier: another possibility is we don't do a 3.0.1, but we do a 3.1 very soon, and then a 3.2 later in Q4, as we seem to be doing very well with progress right now :) [10:52:53] <cescoffier> purplefox: that would be probably the 'safest' as the new feature can be tested [10:53:13] <cescoffier> but that also mean we need to do housecleaning [10:54:29] <cescoffier> actually, would prefer cutting a 3.1 as mid-september we should get the redeploy, the new starter, vert.x shell, stomp, a lot of bug fixes and improvements in web and core [10:54:37] <cescoffier> the need connection pool in jdbc [10:54:55] <cescoffier> and we may be on time for mysql / postgres [10:55:03] <purplefox> it would be nice to get 3.1 out before devoxx too [10:55:21] <purplefox> yep so I agree [10:55:34] <purplefox> btw what do you mean by housekeeping? [10:55:39] <purplefox> in this context [10:56:14] <cescoffier> and sync (forgotten one of the most wanted feature) [10:56:39] <cescoffier> we have lots of examples that need tuning to work on all languages [10:56:59] <cescoffier> we need to create proper manual for a couple of projects [10:57:25] <purplefox> which projects? [10:58:39] <cescoffier> for the manual : [11:01:27] <purplefox> the names are truncated can't see them [11:02:05] <purplefox> annoying that waffle does that [11:04:51] <cescoffier> vertx-service-factory, vertx-maven-service-factory, vertx-jca [11:05:13] <cescoffier> most of the time it's just extracting the content from the file [11:05:47] <purplefox> yeah i guess so, although I wouldn't consider these high priority as most people don't create their own service proxies [11:05:59] <purplefox> and yes, the readmes are pretty good already [11:06:40] <purplefox> on a different note. i notice there are a couple of PRs for changes to Starter from other people. are these superfluous now considering your refactoring? [11:07:07] <purplefox> maybe we should close them saying that soon your changes will take effect so their PRs are redundant [11:09:35] <cescoffier> purplefox: yes all of them are superfluous, as all the 'requested' feature are in the new Launcher [11:09:46] <cescoffier> I will close them once we have the new launcher in place [11:10:05] <cescoffier> that said, I've kept the Starter class for compatibility purpose, and called the new one Launcher [11:10:13] <cescoffier> I let you decide what you want to do [11:10:39] <purplefox> yes, we should keep it so we don't break people's code who are using it [11:10:49] <purplefox> and deprecate it [11:10:59] <purplefox> and remove it in Vert.x 4 i guess [11:11:17] <cescoffier> ok [18:54:53] <zerkz> or a default configuration file name? [18:59:27] <zerkz> is there no default value for -conf argument? [19:54:28] <bq_> what diff between vertx 3 and vertx 2? [19:54:55] <bq_> why there are only 4 languages supported in vertx 3? [19:57:43] <BadApe> only 4? [19:57:51] <BadApe> last time i checked there seemed to be more [20:00:56] <bq_> BadApe: vertx 2 has more than 4. vertx 3 only has 4 right now. for example, python is supported in 2 not in 3 [20:01:28] <BadApe> maybe i am going mad, i thought i saw many more on the release statement [20:01:40] <BadApe> to be honest i am only interested in java [20:01:50] <bq_> on its homepage [20:02:42] <bq_> weird that ruby is supported in 3 but not python. they put ruby before python [23:25:54] * ChanServ sets mode: +o purplefox