If you could wait until the 0.10.0 release vote has been conducted that would be best. Ideally the crates.io release should be performed using the source release tarball. If it cannot, then open a bug report so that it can be fixed for next time.
On Tue, Jul 24, 2018 at 11:09 PM, Andy Grove <andygrov...@gmail.com> wrote: > Yes, I think that makes sense. So should I go ahead and do that whenever > now or is there more involved? > > Also, I'm the only person that can release to crates.io right now so that > is something we should fix. I can grant release privileges to others. > > On Tue, Jul 24, 2018 at 9:04 PM Wes McKinney <wesmck...@gmail.com> wrote: > >> Seems fine to cut a release to crates.io with the 0.10.0 release. Do >> you want to use the same version numbers? >> >> On Tue, Jul 24, 2018 at 11:00 PM, Renjie Liu <liurenjie2...@gmail.com> >> wrote: >> > +1 for pushing to crates.io. >> > >> > On Wed, Jul 25, 2018 at 10:52 AM Andy Grove <andygrov...@gmail.com> >> wrote: >> > >> >> Hi, >> >> >> >> I'm wondering what we should do with the Rust implementation for the >> 0.10.0 >> >> release. I would like to have an official release pushed to crates.io >> for >> >> sure. >> >> >> >> Since the Rust implementation is so new there isn't much demand for new >> >> features yet so I think it is more important to focus on changes that >> will >> >> help to encourage adoption, like examples and better documentation. >> >> >> >> I'm open to suggestions. >> >> >> >> Thanks, >> >> >> >> Andy. >> >> >> > -- >> > Liu, Renjie >> > Software Engineer, MVAD >>
