mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anirudh <anirudh2...@gmail.com>
Subject Re: Regarding MXNet 1.2.0 Release
Date Thu, 12 Apr 2018 04:53:48 GMT
Hi all,

Thanks to the hard work of everyone involved we are down to 2 open required
PRs.
If there are no surprises, we should be able to cut the release branch
tomorrow.

Anirudh

On Wed, Apr 11, 2018 at 9:25 AM, Anirudh <anirudh2290@gmail.com> wrote:

> Hi Marco,
>
> Thank you for pointing. Looking at it now.
>
> Anirudh
>
> On Wed, Apr 11, 2018 at 5:49 AM, Marco de Abreu <
> marco.g.abreu@googlemail.com> wrote:
>
>> Hello,
>>
>> there seems to be a backwards compatibility breaking issue which is
>> tracked
>> at https://github.com/apache/incubator-mxnet/issues/10503. We should
>> follow
>> up with it before the next release.
>>
>> Best regards,
>> Marco
>>
>> On Wed, Apr 11, 2018 at 8:16 AM, Anirudh <anirudh2290@gmail.com> wrote:
>>
>> > Hi all,
>> >
>> > Update on the status for the 1.2 release:
>> >
>> > We currently have 7 required PRs that are currently unmerged:
>> > https://docs.google.com/spreadsheets/d/1iWvZjzZ7ZVfgW8ZfraHkzxwiNuBOa
>> > xpSyYc8Mqn2F2k
>> >
>> > Thanks a lot to all the committers and contributors for the work on
>> merging
>> > the 17 required PRs.
>> >
>> > Anirudh
>> >
>> >
>> > On Mon, Apr 9, 2018 at 11:52 PM, Anirudh <anirudh2290@gmail.com> wrote:
>> >
>> > > Hi all,
>> > >
>> > > Current status for the 1.2 release:
>> > > Total number of required PRs : 25
>> > > Number of required PRs already merged : 5
>> > >
>> > > Among the remaining open, we have 6 PRs which look ready to merge
>> while
>> > > others may require reviews/review followup.
>> > >
>> > >
>> > > Anirudh
>> > >
>> > >
>> > > On Mon, Apr 9, 2018 at 4:32 PM, Anirudh <anirudh2290@gmail.com>
>> wrote:
>> > >
>> > >> Hi all,
>> > >>
>> > >> Please ignore my previous email.
>> > >>
>> > >> We are currently tracking the pending PRs here: <
>> > >> https://docs.google.com/spreadsheets/d/1iWvZjzZ7ZVfgW8ZfraH
>> > >> kzxwiNuBOaxpSyYc8Mqn2F2k>
>> > >> The ones marked Required under "Note" are the ones that we intend to
>> > >> merge for Release 1.2.0.
>> > >>
>> > >> If you are an owner of one of the PRs, I would request you to address
>> > >> comments on the PR if they haven't been addressed yet.
>> > >> If you are a reviewer on one of the PRs, I would request you to
>> followup
>> > >> on the changes and approve if it looks ready to merge.
>> > >>
>> > >> Thanks a lot to all of you for your efforts for the 1.2 release.
>> > >>
>> > >> Anirudh
>> > >>
>> > >>
>> > >> On Mon, Apr 9, 2018 at 4:23 PM, Anirudh <anirudh2290@gmail.com>
>> wrote:
>> > >>
>> > >>> Hi all,
>> > >>>
>> > >>> We are currently tracking the PRs :
>> > >>>
>> > >>>
>> > >>> On Mon, Apr 9, 2018 at 8:14 AM, Steffen Rochel <
>> > steffenrochel@gmail.com>
>> > >>> wrote:
>> > >>>
>> > >>>> We 72 unmerged PR, most of them are related to recent bug fixes.
>> Only
>> > 20
>> > >>>> have not been updated in last 10 days.
>> > >>>> Please review, address feedback and merge as soon as possible,
so
>> we
>> > can
>> > >>>> roll in all your great work to improve the quality into the
>> upcoming
>> > >>>> release.
>> > >>>>
>> > >>>> Thanks
>> > >>>> Steffen
>> > >>>>
>> > >>>> On Fri, Apr 6, 2018 at 8:56 PM Anirudh <anirudh2290@gmail.com>
>> wrote:
>> > >>>>
>> > >>>> > Hi all,
>> > >>>> >
>> > >>>> > I am planning to cut the release branch for 1.2.0 on Monday.
>> Please
>> > >>>> let me
>> > >>>> > know if you have any concerns with the date or any other
>> > suggestions.
>> > >>>> >
>> > >>>> > Anirudh
>> > >>>> >
>> > >>>>
>> > >>>
>> > >>>
>> > >>
>> > >
>> >
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message