We finally got all the pending commits reviewed and merged! The upcoming release(0.3.0) will be cut from current master branch commit ( 9abf0a4b105d624ec310273c2bd7f52c1f3ce12a <https://github.com/apache/incubator-pinot/commit/9abf0a4b105d624ec310273c2bd7f52c1f3ce12a>) as of date: Wed Feb 27 16:09:51 PST 2020.
The release notes is here: https://apache-pinot.gitbook.io/apache-pinot-cookbook/releases/0.3.0 Please let me know if you have any questions. Best, Xiang Fu Xiang <[email protected]> 于2020年2月18日周二 上午3:35写道： > Here is the draft > <https://docs.google.com/document/d/1zCY6KNma3WoHIju9Revp7JUlr4gtIYPPwu6xpJzlY3I/edit?usp=sharing> > for new release notes. > > All comments are welcome. > > Subbu Subramaniam <[email protected]> 于2020年2月16日周日 > 下午1:02写道： > >> The best way to communicate such major change in interface is by updating >> the major version number. >> >> We can say that the software has been restructured significantly to >> accommodate cloud readiness (blog coming up soon) and easy plug n play. >> >> Which was the objective of the re-factor anyway. >> >> What is the reaon NOT to call it 1.0? >> >> -Subbu >> ________________________________ >> From: kishore g <[email protected]> >> Sent: Sunday, February 16, 2020 10:24 AM >> To: [email protected] <[email protected]> >> Subject: Re: Preparing for upcoming Pinot Release >> >> Hi Subbu, >> >> I am with you on significant changes to the package names and the need to >> recompile the code if anyone has the wrapper like LinkedIn. What do you >> think is the best way to communicate this without calling it 1.0. >> >> thanks, >> Kishore G >> >> >> >> >> On Sun, Feb 16, 2020 at 9:40 AM Subbu Subramaniam <[email protected]> >> wrote: >> >> > I disagree. >> > >> > In LinkedIn, we had to change our wrapper software significantly due to >> > the API (and package name) changes. >> > >> > Have you compiled the release notes? That should indicate the amount of >> > changes that went in. >> > >> > -Subbu >> > >> > On 2020/02/16 05:49:16, Fu Xiang <[email protected]> wrote: >> > > Regarding the version, I suggest to still call it 0.3.0 as the >> > > PluginManager is still backward compatible from users' perspective in >> PR: >> > > >> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinot%2Fpull%2F5035&data=02%7C01%7Cssubramaniam%40linkedin.com%7C7fd26a7da6454a3e9cea08d7b30d8d73%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637174743102251978&sdata=o%2Fin2UJZYqX7gvCadZR4Bji4HhSQ1XQ0G8fUC7OkSc0%3D&reserved=0 >> . >> > > >> > > We can leave 1.0.0 for something bigger later. >> > > >> > > On Thu, Feb 13, 2020 at 12:08 Subbu Subramaniam <[email protected]> >> > wrote: >> > > >> > > > Thanks, @kishore g <[email protected]> >> > > > Please do send it out for a review when the docs are ready >> > > > >> > > > thanks >> > > > >> > > > -Subbu >> > > > >> > > > >> > > > On Thu, Feb 13, 2020 at 10:27 AM kishore g <[email protected]> >> > wrote: >> > > > >> > > > > @Siddharth Teotia <[email protected]> Lets get the text PR >> > merged. >> > > > > Will be good to release it as experimental and collect feedback. >> > > > > >> > > > > @Subbu Subramaniam <[email protected]> We have moved all the >> docs >> > from >> > > > > RTD to gitbook. I need to restructure a bit and it will be ready >> to >> > go by >> > > > > the time we make the release. >> > > > > Let's call out all the major changes in 1.0.0 >> > > > > >> > > > > On Thu, Feb 13, 2020 at 9:59 AM Subbu Subramaniam < >> > [email protected]> >> > > > > wrote: >> > > > > >> > > > >> Hi Xiang, >> > > > >> >> > > > >> Thanks for taking on the release work. >> > > > >> >> > > > >> I suppose the version will be 1.0.0? >> > > > >> >> > > > >> Please make sure that: >> > > > >> 1. Either we are migrated fully to the new documentation, OR we >> have >> > > > >> documented all new features in the existing documentation. The >> > current >> > > > >> situation is that neither of these is true. It will be >> unfortunate >> > if we >> > > > >> make a release with documentation in two places, neither of >> which is >> > > > >> complete. I will be willing to help fix the doc issue. Please >> send >> > out >> > > > an >> > > > >> email to committers (or general) providing appropriate >> instructions, >> > > > and we >> > > > >> can have the community fix the documents before the release. >> > > > >> 2. The release notes lists all the incompatiblities introduced, >> and >> > > > >> migration plans, etc. I know of at least one incompatibility. >> You >> > > > cannot >> > > > >> upgrade from 0.1 to 1.0 without going through 0.2, because of >> > > > >> incomaptibolituy introduced in >> > > > >> >> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinot%2Fpull%2F4346&data=02%7C01%7Cssubramaniam%40linkedin.com%7C7fd26a7da6454a3e9cea08d7b30d8d73%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637174743102251978&sdata=4TLJFAfU7Tcd7kM6uz8bgDv2RZJvz6psabJ6h0VUMn0%3D&reserved=0 >> (if you have >> > those >> > > > >> queries, of course). There may be others, given that we have had >> a >> > big >> > > > >> overhaul. >> > > > >> >> > > > >> thanks again >> > > > >> >> > > > >> -Subbu >> > > > >> >> > > > >> >> > > > >> On 2020/02/13 00:08:20, Fu Xiang <[email protected]> wrote: >> > > > >> > Hi Pinot Community, >> > > > >> > >> > > > >> > I'm preparing the upcoming release from current master branch >> > commit ( >> > > > >> > 7cca1442d7ad41705643862b7237f445e8803368 >> > > > >> > < >> > > > >> >> > > > >> > >> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinot%2Fcommit%2F7cca1442d7ad41705643862b7237f445e8803368&data=02%7C01%7Cssubramaniam%40linkedin.com%7C7fd26a7da6454a3e9cea08d7b30d8d73%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637174743102251978&sdata=l0jDcqDS9BZ4rwyiVs9czS%2B6xH6GVI51BpStOqQ%2Fe6A%3D&reserved=0 >> > > > >> >) >> > > > >> > as of date: Wed Feb 12 15:58:31 PST 2020. >> > > > >> > >> > > > >> > Please let me know if you still have any changes wanted to get >> in >> > by >> > > > >> > tomorrow Noon. >> > > > >> > >> > > > >> > Best, >> > > > >> > >> > > > >> > Xiang >> > > > >> > >> > > > >> >> > > > >> >> > --------------------------------------------------------------------- >> > > > >> To unsubscribe, e-mail: [email protected] >> > > > >> For additional commands, e-mail: [email protected] >> > > > >> >> > > > >> >> > > > >> > > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> > >> > > > -- > Xiang Fu > -- Xiang Fu
