Hi,
Is it rather encouraged to get them into 0.14.0, or rather discouraged?
In other words, should as much go into the release as possible, or should
current master already "settle down" to be as stable as possible before
the release?
Of course stable is key. OTOH there may be some feature/bugfix that is kind
of a release blocker for some reason and therefore should be included.
Deciding about a feature set is mostly a question of priorities and it
usuallycomes down to "when can we deliver" vs. "what risks are we taking".
You have time, features, quality and workload. Assumed we won't let down on
quality, there are two options out of three left for you to nail down. The
remaining option is what you have to accept as-is. Basic project management.
If you give us an idea what exactly you are talking about, we might be able
to give some feedback. Hard to tell on "a few PRs in the pipeline", because
it mostly depends on the content.
Have fun,
JensG
-----Ursprüngliche Nachricht-----
From: Mario Emmenlauer
Sent: Wednesday, January 6, 2021 10:35 PM
To: dev@thrift.apache.org ; Yuxuan Wang
Subject: Re: Plans/process for 0.14.0 release?
On 04.01.21 21:41, Yuxuan Wang wrote:
Judging from history the end of the years are usually when we do releases,
is there a plan for 0.14.0 release?
I have a few PRs in the pipeline, that are already reviewed and ready for
merge. I just did not have time to perform the merge yet.
Is it rather encouraged to get them into 0.14.0, or rather discouraged?
In other words, should as much go into the release as possible, or should
current master already "settle down" to be as stable as possible before
the release?
All the best,
Mario Emmenlauer
