It does not seem that anybody has any concern with branching and lifting
the freeze after 4.0-RC is released.
I will take care of it once RC is released.
Do not hesitate to raise your voice if you have some concerns. :-)
On Mon, Mar 29, 2021 at 4:37 PM Benjamin Lerer wrote:
> Thanks for your
Thanks for your answers.
I agree to this proposal but I'm suggesting we close and codify the release
> cadence discussion from [1] before we lift the freeze, and maybe kick off
> the roadmap discussion but we probably shouldn't block the unfreeze on
> this.
>
Sorry, for not closing the release
(mostly reiterating) +1 to branching and unfreezing trunk, and to codifying
the release cadence.
Excited about the 4.0 rc! and looking forward to the roadmap discussion!!
On Thu, Mar 25, 2021 at 8:18 AM Paulo Motta
wrote:
> > My thinking was talking about when to lift the freeze was moot if we
> My thinking was talking about when to lift the freeze was moot if we
hadn't branched, and the agreed upon release lifecycle is pretty clear that
we don't branch until GA. Am I misunderstanding the relationship there?
The proposal of this thread is to branch and lift the freeze before GA.
I
>
> be very practical and codify our existing agreements
> discussed on the mentioned threads before lifting the freeze
Ah. My thinking was talking about when to lift the freeze was moot if we
hadn't branched, and the agreed upon release lifecycle is pretty clear that
we don't branch until GA. Am
> That said, I think freezing feature contribution and not branching until
GA like we've newly done with 4.0 is bad for the health of the project
+1. I think the freeze and branching until GA was atypical and unique to
4.0 and won't be repeated in the upcoming releases. I agree with Sumanth's
The current "Release Lifecycle" wiki doc speaks to when we branch:
https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle
Specifically under "General Availability (GA)":
- A new branch is created for the release with the new major version,
limiting any new feature addition
I agree we should start considering branching 4.0 and unfreezing soon, but
before I think we should:
- Close the loop on the agreed points of the "releases after 4.0" [1] and
"project roadmap" [2] threads and document the new release guidelines
post-4.0 so we have a good starting point.
- Revisit
Hi Benjamin,
Thanks for bringing it up. I support the idea.
I saw more activity from new contributors lately, also Google Summer of
Code is around the corner. Plus I feel it gives a very positive signal
about the state of the project.
The amount of tickets before GA is really quite low. CI is
Hi everybody,
We are now extremely close to releasing 4.0-RC, the number of tickets left
in the 4.0-GA scope is 20 and only 3 of them are not assigned yet. By
consequence, I was wondering if it would make sense to create a 4.0 branch
and unfreeze trunk when we release RC.
The advantages I see
10 matches
Mail list logo
