Fwd: [jira] Commented: (INFRA-2506) SVN repo for new TLP cassandra
heads up. we're moving SVN repo's (and mailing lists etc etc) Begin forwarded message: > From: "Joe Schaefer (JIRA)" > Date: March 14, 2010 9:56:27 AM GMT+11:00 > To: i...@holsman.net > Subject: [jira] Commented: (INFRA-2506) SVN repo for new TLP cassandra > > >[ > https://issues.apache.org/jira/browse/INFRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844980#action_12844980 > ] > > Joe Schaefer commented on INFRA-2506: > - > > Will move subversion in the next hour or so unless someone objects. > >> SVN repo for new TLP cassandra >> -- >> >>Key: INFRA-2506 >>URL: https://issues.apache.org/jira/browse/INFRA-2506 >>Project: Infrastructure >> Issue Type: Task >> Security Level: public(Regular issues) >> Components: Subversion >> Reporter: Ian Holsman >> >> Hi Infra. >> on Feb 17 the cassandra project graduated to a TLP. >> can someone please set up the repo so we can switch the stuff over to the >> new place. >> (I'm assuming you need to do something for this.. if not my apolagies) >> Thanks once again! > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > -- Ian Holsman i...@holsman.net
IMPORTANT: mailing lists are moving
Hi guys. As most of you are aware, cassandra is now a top level project. so as part of that the mailing lists are moving over to their new place, and the current incubator ones will close down. there are >3< mailing lists. cassandra-...@incubator... is now dev@cassandra.apache.org cassandra-u...@incubator... is now u...@cassandra.apache.org cassandra-comm...@incubator.. is now comm...@cassandra.apache.org to subscribe send an email to the following: dev-subscr...@cassandra.apache.org user-subscr...@cassandra.apache.org commits-subscr...@cassandra.apache.org -- Ian Holsman i...@holsman.net
Re: IMPORTANT: mailing lists are moving
BTW.. your existing subscriptions have been moved over.. there is no need to re-subscribe.. just to alter where you post to in the future. sorry for the confusion. On 3/14/10 10:09 AM, Ian Holsman wrote: Hi guys. As most of you are aware, cassandra is now a top level project. so as part of that the mailing lists are moving over to their new place, and the current incubator ones will close down. there are>3< mailing lists. cassandra-...@incubator... is now dev@cassandra.apache.org cassandra-u...@incubator... is now u...@cassandra.apache.org cassandra-comm...@incubator.. is now comm...@cassandra.apache.org to subscribe send an email to the following: dev-subscr...@cassandra.apache.org user-subscr...@cassandra.apache.org commits-subscr...@cassandra.apache.org -- Ian Holsman i...@holsman.net
IMPORTANT: SVN repo has moved
it should be as easy as going $ svn switch https://svn.apache.org/repos/asf/cassandra/trunk the website cassandra.apache.org will slowly come up and reflect these changes. mirrors and mail-archivers will need to be notified about the switch.. so we'll be in a minor state of flux while this happens.
Re: [VOTE] Release 0.6.0-beta3
+1 [binding] On 3/18/10 7:13 AM, Jonathan Ellis wrote: +1 [binding] On Wed, Mar 17, 2010 at 2:17 PM, Eric Evans wrote: It's been a bit since the last beta, and while many important fixes have made their way in[1], we're still not quite ready to roll a release candidate. I propose one more beta in order to get some of this new work tested while we're closing out the remaining issues[2]. Tag and artifacts for 0.6.0-beta3: SVN Tag: https://svn.apache.org/repos/asf/cassandra/tags/cassandra-0.6.0-beta3 0.6.0-beta3 artifacts: http://people.apache.org/~eevans Obviously this is a +1 from me. :) [1]: https://svn.apache.org/repos/asf/cassandra/tags/cassandra-0.6.0-beta3/CHANGES.txt [2]: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310865&fixfor=12314361 -- Eric Evans eev...@rackspace.com
Re: Binary release artifacts (or What a User Wants)
On 3/18/10 8:21 AM, Eric Evans wrote: During the 0.6 cycle Ivy was introduced to manage (most of) our dependencies, and where possible, jars were removed from svn and no longer included in binary release artifacts. Recently though this change has been called into question, with some discussion taking place in CASSANDRA-850[1]. The 0.6 release is upon us, but if consensus will be to rollback this change and resume the practice of embedding third-party jars, I strongly feel we should do that now. I don't want to see 0.6 as a one-off that we're forced to explain over and over. my opinion is to keep ivy. from what you said it is relatively painless for a customer to get the 3rd party jars via ivy-retrieve on their build machine. and I really hope people aren't just grabbing the jar file and deploying it in production ;-0 I don't see any negatives, except for the crazy developer who downloads the jar and gets on a plane for 5 hours, and kicks himself when he realizes he can't code. BACKGROUND We've seen a steadily increasing list of dependencies, but it really exploded between 0.5 and 0.6 (think 2x). This was causing a number of problems: 1. First and foremost, we were doing a less than perfect job of maintaining licensing and attribution. The exact requirements here depend on a number of variables and are fraught with subtleties. Failure to get this right creates legal risks that the ASF finds unacceptable so doing it poorly is really not an option. Ivy "fixed" this problem by side-stepping the issue entirely. If we aren't shipping it, then there is simply no need to maintain this documentation. 2. Many of these dependencies have dependencies in turn (and so on). Sometimes these dependencies (or the dependencies of the dependencies, etc) share dependencies with other dependencies, but with different versions. Sound confusing? It can be, yes, and the complexity seems to grow exponentially to the number of jars we're pulling in. Ivy fixed this problem because this is precisely what Ivy does, it resolves a graph of your project dependencies based on a specification (ivy.xml), and retrieves them. Or to put all of this more simply... tedious, time consuming, and error prone tasks were automated away. This however did not come without a price, and the costs that I see in order of importance are: 1. Downloading arbitrary code off the 'net, (and without a good trust path). 2. Requiring networking connectivity at install time. 3. Requiring ant to be present at install time. 4. One extra step in the install process, (i.e. invoking `ant ivy-retrieve') I know a lot of people wouldn't consider (1) and (2) to be real issues, (just look at how popular Maven is), so YMMV. I personally don't think (3) and (4) are that onerous but I can't disagree with the weird-to-require-a-build-tool argument, or that one more step in Getting Started is still one more step. So to me, this boils down to deciding whether the cure is worse than the disease. Thoughts? [1]: https://issues.apache.org/jira/browse/CASSANDRA-850
Re: Binary release artifacts (or What a User Wants)
On 3/19/10 5:36 AM, Jesse McConnell wrote: yes, and my point is that if there is any question in your guys minds on if it is allowed or not that is an issue for apache legal (via jira) for a definitive answer so.. if you have a question for them.. go ping them.. no need anyone else to paraphrase it.. just go ahead and ask. I am not a lawyer, but I'll play one on a mailing list.. please don't. it doesn't help anyone. if you think you need a legal opinion then get one. you (and your companies) circumstances are unique, and as such you should hire your own legal representation to analyze the situation and how it works in your circumstances. (called a legal opinion I think) don't assume that your circumstances meet the need of the general public as every one is different. we as a project do our best effort to make sure we have the right attribution and licensing. but we are not lawyers, and our interpretation of what a license means might be different than yours. even lawyers who have looked at these things aren't 100% in agreement to what cross-linking and stuff like that means as it hasn't gone through a legal case where a judge has made a ruling which makes it harder to point to something and say this is the right stuff. so .. let me repeat. if you think there is an issue, get your own lawyer to read the licenses and give you their legal opinion and follow that. that is what they are there for. Ivy and maven downloading dependent jars seems to work well for most projects. the legal thing about if they/can't they has been discussed to death a million times.. go google it. there is no right answer. cheers! jesse
Re: Gsoc2010 proposal
please just keep this conversation on a single list. the mentors for cassandra read all 3 of them.. no need for them to read it 3 times. On 3/26/10 2:19 PM, Ben Standefer wrote: Priyanka, I think our listserv might be dropping your attachment. Please send it directly to me at benstande...@gmail.com. -Ben On Fri, Mar 26, 2010 at 10:41 AM, Priyanka Sharma wrote: Hi I am Priyanka Sharma, master student at Vrije University, Amsterdam. My major is "parallel and distributed system system". I am interested to participate in gsoc2010 with cassandra. I would like to implement "demo application for cassandra". I have attached my proposal(not fully final) with this email and also my CV for your reference. I would like to have your comments on my proposal, So that I can make it better. Kindly give me some feedback about my proposal. -- Thanks& Regards Priyanka
Re: [VOTE] 0.7.0-beta1
+1
Incremental counters
Hi. apologies in advance, as I haven't been keeping current on what is going on in cassandra-land for a while. I noticed that incremental counters have been added to 0.8/Trunk in CASSANDRA-1072. I was wondering if this (and supporting patches?) could be easily applied to 0.74, or if the current trunk is stable enough to use. I think twitter is using this in their Rainman product.. ideally they will release that soon as well ;-) Thanks in advance --Ian
Re: Doc on API change from Cassandra 0.7 to 0.8
Cassandra recently moved to thrift 0.6, which caused the interface files to change in an incompatible way. This is probably the major issue. On Apr 14, 2011, at 1:56 PM, Shariq wrote: > Hi Devs, > > I am trying to build Hector against Cassandra 0.8, and have some bumpers > cause there have been some major API changes, around thrift I suppose? Could > someone please point me to a docs/reference that would help me understand > these changes and build Hector working for Cassandra 0.8? > > Thanks, > Shariq.
Re: [VOTE] Release Apache Cassandra 0.8.0
my suggestion would be to release 0.8.0, and work on 0.8.1 to be released in the next couple of weeks with this bug-fix and others that you might find. you can put a note in the README/release notes on how to get pig running with 0.8.0. regards Ian On May 25, 2011, at 12:19 PM, Jonathan Ellis wrote: > I guess you could call it either way, but enough people depend on Pig > these days that we wanted to move it into core for 0.8. It's still in > contrib/ because nobody actually had the time to do the requisite ant > wrangling, but it's effectively as important as the o.a.c.hadoop > package (which is where we want to move it). > > No, I would not re-roll a release to fix example code. > > On Wed, May 25, 2011 at 11:02 AM, Eric Evans wrote: >> On Tue, 2011-05-24 at 22:22 -0500, Jonathan Ellis wrote: >>> Pig is broken in this build; Brandon fixed it in r1127188. >> >> Are we blocking releases for contrib and example code now? >> >> -- >> Eric Evans >> eev...@rackspace.com >> >> > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com
