Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of ContentsmaxLevel
1

About this meeting

This meeting is held triweekly. Topics order by this rule: Things/Rules update < Things to decision < [Regular] MEPs < Others

Important Links:

...

Requested Discussions


Agenda / Minutes

Feel Free to fill in the topics if you are interested to share what you want to do.

June. 6th, 2022()

Save the link to your calendar so you won't miss the meeting!

Zoom link: 

Meeting ID: 556 702 7843

Join Zoom Meeting:

April. 27th, 2022()

Save the link to your calendar so you won't miss the meeting!

Zoom link: 

Meeting ID: 556 702 7843

Join Zoom Meeting: https://zoom.us/j/5567027843

Meeting at 19:00-20:00 PT(Pacific Time) on April 27th/ 11:00 AM China Standard time on April 28th. Not sure when is your local time? Click here to convert to your time zone.

...

Mar. 23rd, 2022(Recording)

Save the link to your calendar so you won't miss the meeting!

Zoom link: https://zoom.us/j/5567027843

Meeting no. 556 702 7843

Meeting at 19:00-20:00 PT(Pacific Time) on Mar. 23rd/ 11:00 AM China Standard time on Mar. 24th. Not sure when is your local time? Click here to convert to your time zone.

Feb. 16th, 2022(Recording)

Save the link to your calendar so you won't miss the meeting!

Zoom link: https://zoom.us/j/5567027843

Meeting no. 556 702 7843

Meeting at 19:00-20:00 PT(Pacific Time) on Feb.16th/ 11:00 AM China Standard time on Feb.17th. Not sure when is your local time? Click here to convert to your time zone.

  • Topics
    •  [sunby] multi memory replica design
    •  [haorenfsa] restful API implementation detail
    •  [Sida Shen] Mentorship Program of Milvus community 

Jan. 19th, 2022 (Recording)

Postpone to Jan 19 due to 2.0 GA release

To join the meeting, please register here to receive a Zoom invitation!

Meeting at 19:00-20:00 PT(Pacific Time) on Jan.19th/ 11:00 AM China Standard time on Jan.20th. Not sure when is your local time? Click here to convert to your time zone.

  • Topics
    • [xiaofan-luan] Feature Plans of Milvus 2.1
    • [Yui] Progress of Milvus on MAC (MEP 21 )
    • [godchen] Support Milvus on local disk (MEP 22 )

sDec 7th, 2021 

To join the meeting, please register here first, then we'll send you a Zoom invitation to your email address: 

Meeting at 19:00-20:00 PT(Pacific Time).  11:00-12:00 China Standard time Convert to your time zone.

  • Topics
    • [yanliang567] 2.0 GA current test states 
    • [csz007]Anns Performance Benchmark result and further performance optimization
    • [jaime0815]Make Milvus compilation easier  


Nov 3rd, 2021 2021.11.4tech.mp4

To join the meeting, please register here first, then we'll send you a Zoom invitation to your email address: https://milvus.typeform.com/to/DNDk6A5B

Meeting at 619:00-720:00 PT(Pacific Time).  2110:00-2211:00 China Standard time Convert to your time zone.

  • Topics
    • [weizhi]  On disk hybrid Index design (slides)
    • [

...

Oct 11th, 2021

To join the meeting, please register here first, then we'll send you a Zoom invitation to your email address: https://milvus.typeform.com/to/DNDk6A5B

Meeting at 19:00-20:00 PT(Pacific Time).  10:00-11:00 China Standard time Convert to your time zone.


Sep 8th,2021 (Recording)

Due to lack of attendees, we decide to postone the meeting to next week.

...

  • Topics
    • [yanliang] Milvus 2.0 rc release schedule and quality requirement 
    • [xiangyu] MEP-9 Support delete in Milvus 2.0
    • [xiaofan] Java SDK design plan (MEP 14 -- Offer Milvus 2.0 JAVA SDK(TBD)SDK)


Aug 11th, 2021 (Recording)

...

  • Topics
    •  [xiaofan] what’s inside Milvus 2.0 and the time schedule (Milvus 2.0 Long Term Roadmap and Time schedule
      • Reach the agreement about Milvus milestones and things to do. 
    •  [yefu] MEP workflow
      • assign a number to each MEP page
      • put the mep workflow on the confluence page
    •  [yangxuan] Merge PyMilvus and PyMilvus-ORM repo
      • Keeping which repo: PyMilvus

      • Keeping which set of API:

        • step1: both, and we mark PyMilvus API as `deperacated`

        • step2: pymilvus-orm

      • Keeping which package name: pymilvus

    •  [xiangyu] Update OWNERS files
      • Not good in tech meetings, to try the mailing list

...