Thanks very much for this information-- it is indeed very helpful. This statement:
> Indeed, the trunk branch has been frozen for new feature inclusion for quite > some time, and there have been some limited discussions on how long this > might be. "When it's done" is basically the current answer, while the > existing in-flight, approved feature jiras are still in progress or under > review. is the most precise and concise description I've been able to get of the situation. I'll leave the ticket open since other people were interested in the feature but leave it to them to pursue, or I can certainly close the ticket if that seems better. > This is an example of a possible problem with a long-frozen trunk branch - > new things may need to sit in limbo for a while, until cassandra-4.0 is > branched and there is an opportunity to commit new features to trunk again. Speaking only for myself, the problem is not exactly a long-frozen trunk branch-- the problem is that there is no date (not even a prospective date) at all for the end of that freeze and so I cannot prepare for it. For the task I wanted to solve with 15005 I will take a different approach, because I cannot plan to use Cassandra in my environment if I cannot assume anything at all about when releases will be made. Thanks! ajs6f > On Jul 8, 2019, at 12:37 PM, Michael Shuler <mich...@pbandjelly.org> wrote: > > On 7/3/19 1:44 PM, aj...@apache.org wrote: >> In fact there is a branch for it noted in the ticket, from which a >> patch could be cut instantly, but there doesn't seem to be any point >> to doing that until the feature freeze is over. Is there any sense of >> timing on that? I've seen a few discussions about release process for >> 4.x on this list, but I haven't been able to get a sense of how long >> it might be. > > I see a couple different links to a couple different branches and a github > compare with conflicts in comments in CASSANDRA-15005. I see no PR link, and > the project doesn't use PRs in practice. There is no patch attached to the > jira. I also see a link to an open related jira and discussion around that. I > don't know the details of the actual feature/improvement, but the discussion > appears (to me) to still be a discussion. It does not look (to me) like a > finalized patch with completed CI links, etc. ready for someone to review. > Regardless, it does not appear (to me) to be appropriate for 3.11.x. > > The cassandra-3.11 branch is in maintenance mode, which means no new > features. Improvements require discussion and consensus for inclusion in > maintenance branches, in order to keep breaking changes to a minimum. New > features should target the trunk branch (4.0), unless there is a previously > obtained consensus to include a particular improvement/feature in an earlier > branch. Indeed, the trunk branch has been frozen for new feature inclusion > for quite some time, and there have been some limited discussions on how long > this might be. "When it's done" is basically the current answer, while the > existing in-flight, approved feature jiras are still in progress or under > review. > > With trunk frozen, this feature may need to simply wait. This is an example > of a possible problem with a long-frozen trunk branch - new things may need > to sit in limbo for a while, until cassandra-4.0 is branched and there is an > opportunity to commit new features to trunk again. > > I hope that helps! Some of the above is definitely my understanding and some > subjective observation of that specific jira. > > (An update on the current state of in-progress/review statuses for 4.0 jiras > from the folks working on them would be awesome! hint hint.) > > Kind regards, > Michael > >> On Wed, Jul 3, 2019, 1:28 AM Mick Semb Wever <m...@apache.org >> <mailto:m...@apache.org>> wrote: >>> Is there any chance to get CASSANDRA-15005 (ready, with PR) into a 3.11.5 >>> release? >> I doubt it Soroka. It's not a bug and there's no patch for it, so I'd >> see no reason why Michael would wait for this when he generously >> finds time to cut a release. >> Maybe the author and reviewer decides to push it to both 3.11.x and >> 4.0, but that's irrelevant to this thread. >> regards, Mick >> --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > <mailto:dev-unsubscr...@cassandra.apache.org> >> For additional commands, e-mail: dev-h...@cassandra.apache.org >> <mailto:dev-h...@cassandra.apache.org> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
