Re: Time for a new 3.0/3.11 release?
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 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 > <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
Re: Time for a new 3.0/3.11 release?
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. ajs6f On Wed, Jul 3, 2019, 1:28 AM Mick Semb Wever 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>
Re: Time for a new 3.0/3.11 release?
Is there any chance to get CASSANDRA-15005 (ready, with PR) into a 3.11.5 release? I understand that there is a feature freeze, but I do see some small tickets (eg. CASSANDRA-15090) that would seem to have been merged for release, and I think 15005 is quite small, too. I'm happy to do whatever I can to help this happen. The current branch for 15005 is for 4.x, but it was originally written by Jon Meredith for 3.x and I could easily move it back to that line. Thanks! ajs6f > On Jul 2, 2019, at 6:23 AM, Mick Semb Wever wrote: > > >> I will try and wrap up my review of 14812 today. > > > CASSANDRA-14812 has been committed. > > - > 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
Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?
+1 in the fullest degree. A date that needs to be changed is still enormously more attractive than no date at all. Adam Soroka > On May 23, 2019, at 12:01 PM, Sumanth Pasupuleti > wrote: > > Having at least a ballpark target on the website will definitely help. +1 > on setting it to Q4 2019 for now. > > On Thu, May 23, 2019 at 8:52 AM Dinesh Joshi wrote: > >> +1 on setting a date. >> >> Dinesh >> >>> On May 23, 2019, at 11:07 AM, Michael Shuler >> wrote: >>> >>> We've had 4.0 listed as TBD release date for a very long time. >>> >>> Yesterday, Alexander Dejanovski got a "when's 4.0 going to release?" >> question after his repair talk and he suggested possibly Q4 2019. This >> morning Nate McCall hinted at possibly being close by ApacheCon Las Vegas >> in September. These got me thinking.. >>> >>> Think we can we shoot for having a 4.0 alpha/beta/rc ready to >> announce/release at ApacheCon? At that time, we'll have been frozen for 1 >> year, and I think we can. We'll GA release when it's ready, but I think Q4 >> could be an realistic target. >>> >>> With that said, I'd like to change "TBD" on the downloads page to "Est. >> Q4 2019". We can always push or pull the estimate, but I think it's time to >> have a goal line. This lines up with ApacheCon nicely for a preview release. >>> >>> Any concerns or objections to editing the download page? Have some other >> goal timeframe in mind? >>> >>> -- >>> Warm regards, >>> Michael >>> >>> - >>> 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 >> >> - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: [jira] [Commented] (CASSANDRA-15005) Configurable whilelist for UDFs
Yes, IIUC, all version branches are either frozen to get to release or
bugfixes-only [1]. I'm not quite sure where new potential features are to go--
perhaps just parked in branches/PRs until the release of 4.0? In any event, I'm
happy to do whatever is appropriate for a new feature, of course.
I've rebased it onto trunk [2] and indeed, it needed only a few lines of
rewriting (ProtocolVersion was apparently added recently enough to matter). Now
I'll get onto trying to add some more tests (again, mostly to prove that I
understand the feature) and some prospective documentation. Thanks Jon Meredith!
ajs6f
[1]
https://cassandra.apache.org/doc/latest/development/patches.html#choosing-the-right-branches-to-work-on
[2] https://github.com/ajs6f/cassandra/blob/CASSANDRA-15005-trunk
> On Mar 15, 2019, at 1:12 PM, Jon Meredith wrote:
>
> I don’t think it will need too much rewriting, and you’re welcome to give
> it a go. However trunk is mostly feature frozen while it undergoes testing
> ahead of release.
>
> On Fri, Mar 15, 2019 at 9:43 AM A. Soroka (JIRA) wrote:
>
>>
>>[
>> https://issues.apache.org/jira/browse/CASSANDRA-15005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793710#comment-16793710
>> ]
>>
>> A. Soroka commented on CASSANDRA-15005:
>> ---
>>
>> [~jmeredithco] I just realized that your branch being from the 3.0 line
>> means it runs up against the code freeze for that branch. I didn't
>> understand what you meant by writing "I'm also not sure what version this
>> could land in with the current freeze on trunk." but now I see that there's
>> a problem there. I can try rewriting this patch for {{trunk/4.0}} if you
>> think that would be feasible/better?
>>
>>> Configurable whilelist for UDFs
>>> ---
>>>
>>>Key: CASSANDRA-15005
>>>URL:
>> https://issues.apache.org/jira/browse/CASSANDRA-15005
>>>Project: Cassandra
>>> Issue Type: Improvement
>>> Components: CQL/Interpreter
>>> Reporter: A. Soroka
>>> Priority: Low
>>>
>>> I would like to use the UDF system to distribute some simple
>> calculations on values. For some use cases, this would require access only
>> to some Java API classes that aren't on the (hardcoded) whitelist (e.g.
>> {{java.security.MessageDigest}}). In other cases, it would require access
>> to a little non-C* library code, pre-distributed to nodes by out-of-band
>> means.
>>> As I understand the situation now, the whitelist for types UDFs can use
>> is hardcoded in java in [UDFunction|[
>> https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/functions/UDFunction.java#L99]
>> .]
>>> This ticket, then, is a request for a facility that would allow that
>> list to be extended via some kind of deployment-time configuration. I
>> realize that serious security concerns immediately arise for this kind of
>> functionality, but I hope that by restricting it (only used during startup,
>> no exposing the whitelist for introspection, etc.) it could be quite
>> practical.
>>> I'd like very much to assist with this ticket if it is accepted. (I
>> believe I have sufficient Java skill to do that, but no real familiarity
>> with C*'s codebase, yet. :) )
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v7.6.3#76005)
>>
>> -
>> To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
>> For additional commands, e-mail: commits-h...@cassandra.apache.org
>>
>>
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
