I had an action from the last call to create a Google doc for us to
collaborate on for a blog post announcing 3.0.0. Here is the document. I
didn't get a chance to actually fill out much but hopefully, we can all
contribute to this.

https://docs.google.com/document/d/1HfdmVE9iQcYlWyfk68BN2PcIjAAhRFpuPLsZW6ffy3Y/edit?usp=sharing



On Wed, Jan 27, 2021 at 5:27 AM Jorge Cardoso Leitão <
jorgecarlei...@gmail.com> wrote:

> Hi,
>
> Thanks a lot for driving this, Andrew.
>
> I agree with what both of you wrote here :)
>
> Best,
> Jorge
>
>
> On Tue, Jan 26, 2021 at 6:06 PM Rémi Dettai <rdet...@gmail.com> wrote:
>
> > Great topics Andrew, to my knowledge nothing has been decided on these
> > topics.
> >
> > We also agreed last time that it would be nice to go round the table so
> > that each of us has an opportunity to present briefly its use case for
> the
> > Rust Arrow implementation.
> >
> > Remi
> >
> > Le dim. 24 janv. 2021 à 13:16, Andrew Lamb <al...@influxdata.com> a
> écrit
> > :
> >
> > > I would like to propose two items for discussion at the Rust sync up
> > > meeting on Wednesday, or comment via email if you would prefer:
> > >
> > > *Item 1: API Backwards compatibility expectations*
> > > What, if any, expectations should users of the Rust Arrow API have
> > > regarding having about needing to change their code when upgrading
> arrow?
> > > Should different parts of the library (eg. Arrow vs DataFusion, or
> > certain
> > > Arrow modules) have different expectations?
> > >
> > > *Item 2: What are the expectations for merging a PR?*
> > > Do we have (or want to have) a more formal set of criteria for merging
> > PRs?
> > > For example, Is a single PR approval enough? Is there any requirement
> on
> > > approvals (e.g. from a committer?)  Is there some minimum time between
> > > approval and merge so others can comment, are there different people
> who
> > > should review / approve different parts of the code?
> > >
> > > I apologize if this is already written down somewhere, but I could not
> > find
> > > it.
> > >
> > > Andrew
> > >
> >
>

Reply via email to