Exactly, 1.2.2 addressing the warning issue. Specially since 1.3.0 is being
already discussed at dev@. Anyway, the podling can learn from these things.
On Tue, Jul 3, 2018, 00:34 Justin Mclean wrote:
> Hi,
>
> > Agree with Dave: incubating releases are not cheap…
>
> Also agree. Seems to me like
Hi,
> Agree with Dave: incubating releases are not cheap…
Also agree. Seems to me like something that could be improved on in a later
release - release early and often! [1]
Thanks,
Justin
1. https://en.wikipedia.org/wiki/Release_early,_release_often
Agree with Dave: incubating releases are not cheap...
On Mon, Jul 2, 2018, 20:02 Anirudh wrote:
> Hi Dave,
>
> Thank you for your inputs. To give more context, the reason we are doing
> the release is to fix a backwards incompatible change with the save_params
> API. This issue impacted some of
Hi Dave,
Thank you for your inputs. To give more context, the reason we are doing
the release is to fix a backwards incompatible change with the save_params
API. This issue impacted some of our users and the warning message in RC0
showed an alternative API for one use case but not the other when
s
Mentors all - Releases are not cheap and we are all volunteers.
Can we teach Release Managers to have a little more judgement about when to
pull a release?
It seems to be too risk adverse to cancel this vote due to a warning message.
My 2 cents.
Regards,
Dave
Sent from my iPhone
> On Jul 2,
Hi,
We are cancelling this vote because we need to improve the warning message
when users use a deprecated API: `save_params`. We will address the issue
and send out a new release for another vote.
Thanks,
Anirudh
