Return-Path: Delivered-To: apmail-incubator-connectors-dev-archive@minotaur.apache.org Received: (qmail 13367 invoked from network); 6 Dec 2010 20:11:02 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 Dec 2010 20:11:02 -0000 Received: (qmail 83490 invoked by uid 500); 6 Dec 2010 20:11:02 -0000 Delivered-To: apmail-incubator-connectors-dev-archive@incubator.apache.org Received: (qmail 83415 invoked by uid 500); 6 Dec 2010 20:11:02 -0000 Mailing-List: contact connectors-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: connectors-dev@incubator.apache.org Delivered-To: mailing list connectors-dev@incubator.apache.org Received: (qmail 83407 invoked by uid 99); 6 Dec 2010 20:11:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Dec 2010 20:11:02 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of daddywri@gmail.com designates 209.85.216.175 as permitted sender) Received: from [209.85.216.175] (HELO mail-qy0-f175.google.com) (209.85.216.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Dec 2010 20:10:56 +0000 Received: by qyk8 with SMTP id 8so3695794qyk.6 for ; Mon, 06 Dec 2010 12:10:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=AVUCTzCBrCkPLUoc8Y6EkAlV4IZKKyFrLY7l/YhXkPM=; b=WNo4VgBVRN3Ao/flrRdxTe6XEN2k4ck4XziIWJtPEbf8pSvmSlvL11SSTGyS6M0/oz f5NbtABmwtvxaFQ3EuSaawQfSwc4D76P/WMHGdxCj2RqBoPJl5u2wBJ/b/tTZgEiHeQ2 g400eO0dizm1/eufCRUSAm1ojZD/q8PBoEcQI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=jJdiVu6oFrpptSIP6w62pVEpRTdO7vVak1BmVDtRHXAdgdgSnrJ5px5NLKvwfUGa+A oy3nI+qc+WsvLdfg218wWv8OfWGB3DjRPiBdNevTFjHnv2eW7qgQ+olye/1OQKO7kp1H AzBtmHGKKokmccaCXRbIu+JKEXak5AIrySw7Y= MIME-Version: 1.0 Received: by 10.229.224.136 with SMTP id io8mr4848714qcb.88.1291666235384; Mon, 06 Dec 2010 12:10:35 -0800 (PST) Received: by 10.229.85.70 with HTTP; Mon, 6 Dec 2010 12:10:35 -0800 (PST) In-Reply-To: References: <6BB3FB84-AF4E-4E7F-80A1-17F9E80DB2D5@apache.org> <5F9A6C381D444589BC97CA1192594CDC@JackKrupansky> <194D8C61B2FE47C4AB9AF6D75D26AEF4@JackKrupansky> <998CF8FF233A473A85FAD8D190B7CFB0@JackKrupansky> <98B9252C244C4F8ABAA3250B467E41BF@JackKrupansky> <86BCDBC2-2FE4-40FF-BA45-F5DB80DB8BD3@apache.org> <56CD890C-6200-4AE5-9092-B7F18DAAE502@apache.org> <81614BC4-4E9D-4870-A1B3-A5003DF7CE7F@apache.org> Date: Mon, 6 Dec 2010 15:10:35 -0500 Message-ID: Subject: Re: Release? From: Karl Wright To: connectors-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Does this also apply to the top-level directory in the tar or zip as well? or can that be left as "apache-manifoldcf-0.1"? Karl On Mon, Dec 6, 2010 at 3:05 PM, Grant Ingersoll wrote= : > FYI, I think the package name needs to have the words incubating in it to= o, as in manifoldcf-0.1-incubating.tar.gz > > -Grant > On Dec 6, 2010, at 8:55 AM, Karl Wright wrote: > >> ... going twice ... >> >> Karl >> >> On Sun, Dec 5, 2010 at 11:42 AM, Karl Wright wrote: >>> I'm done with (1), (4), and (5). =A0Still waiting for help with (2) and >>> (3)... going once.... >>> >>> Karl >>> >>> On Thu, Dec 2, 2010 at 10:02 PM, Karl Wright wrote= : >>>> OK, so I will do the appropriate things to make (1), (4), and maybe >>>> (5) happen. =A0Does anyone want to help with (2), (3), and (8)? >>>> Karl >>>> >>>> On Thu, Dec 2, 2010 at 9:59 PM, Grant Ingersoll = wrote: >>>>> >>>>> On Dec 2, 2010, at 9:54 PM, Karl Wright wrote: >>>>> >>>>>> Hi Grant, >>>>>> >>>>>> In offline conversation you clarified that for (1) you are looking f= or >>>>>> the top level dir in the zip/tar to be named "apache-manifoldcf-0.1"= . >>>>>> You also seem to be asking for a number of other fixes that are >>>>>> specific to a release, that I presume would NOT be in sources on tru= nk >>>>>> (e.g. CHANGES.txt). =A0Are you envisioning that we make these specif= ic >>>>>> changes in the release branch only? >>>>> >>>>> It's perfectly fine for CHANGES.txt to be on trunk. =A0You make the c= hange marking it as 0.1. =A0Once the release is out, you add a new section = at the top for trunk again. >>>>> >>>>> Later, as we mature, we will likely have branches, etc. for this stuf= f, but for now let's just assume trunk is under code freeze and the only ch= anges that can be made are those related to release. >>>>> >>>>> >>>>>> >>>>>> Karl >>>>>> >>>>>> On Thu, Dec 2, 2010 at 9:45 PM, Grant Ingersoll wrote: >>>>>>> We're close, but I think we've got a few more things to do. =A0I di= d get it to compile. >>>>>>> >>>>>>> Notes: >>>>>>> >>>>>>> 1. We should package the stuff all under apache-manifold-0.1 so tha= t when we unzip it's all in one folder. >>>>>>> 2. Many of the libs require an entry in the NOTICE.txt file >>>>>>> 3. =A0All licenses for those libs need to be appended on to the end= of the LICENSE.txt file (See Solr's for instance) >>>>>>> 4. The CHANGES.txt file should reflect that it is a release and not= trunk (not critical to fix) >>>>>>> 5. Is there anyway to make the package smaller? =A0Maybe we don't n= eed to ship both PDF and HTML for the docs. =A0Anything else we can trim? >>>>>>> 6. What's json/org/json all about? >>>>>>> 7. I still see Memex stuff in connectors dir. =A0I didn't check oth= er places. >>>>>>> 8. We should hook in RAT (see Solr's build file) to verify that all= source files have appropriate license headers >>>>>>> >>>>>>> Other than that, some other eyes on it would be good. >>>>>>> >>>>>>> -Grant >>>>>>> >>>>>>> On Dec 2, 2010, at 8:51 PM, Karl Wright wrote: >>>>>>> >>>>>>>> Done >>>>>>>> Karl >>>>>>>> >>>>>>>> On Thu, Dec 2, 2010 at 8:49 PM, Karl Wright w= rote: >>>>>>>>> ok - I might move it there >>>>>>>>> Karl >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Dec 2, 2010 at 8:31 PM, Grant Ingersoll wrote: >>>>>>>>>> Weird, ~kwright doesn't resolve for me on people.a.o, but I can = get to /x1/home/kwright >>>>>>>>>> >>>>>>>>>> FWIW, if you have a public_html directory in your directory and = then place the files there, everyone can download them and check them out a= t http://people.apache.org/~kwright/ >>>>>>>>>> >>>>>>>>>> -Grant >>>>>>>>>> >>>>>>>>>> On Nov 23, 2010, at 1:00 PM, Karl Wright wrote: >>>>>>>>>> >>>>>>>>>>> While I was looking for a solution, an upload attempt succeeded= ! >>>>>>>>>>> >>>>>>>>>>> So there is now an RC0 out on people.apache.org/~kwright: >>>>>>>>>>> >>>>>>>>>>> [kwright@minotaur:~]$ ls -lt manifoldcf-0.1.* >>>>>>>>>>> -rw-r--r-- =A01 kwright =A0kwright =A0 =A0 =A0 =A0 63 Nov 23 17= :57 manifoldcf-0.1.tar.gz.md5 >>>>>>>>>>> -rw-r--r-- =A01 kwright =A0kwright =A0 =A0 =A0 =A0 60 Nov 23 17= :57 manifoldcf-0.1.zip.md5 >>>>>>>>>>> -rw-r--r-- =A01 kwright =A0kwright =A0158734230 Nov 23 17:55 ma= nifoldcf-0.1.zip >>>>>>>>>>> -rw-r--r-- =A01 kwright =A0kwright =A0156742315 Nov 23 17:06 ma= nifoldcf-0.1.tar.gz >>>>>>>>>>> [kwright@minotaur:~]$ >>>>>>>>>>> >>>>>>>>>>> Please let me know what you think. >>>>>>>>>>> Karl >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Tue, Nov 23, 2010 at 11:25 AM, Karl Wright wrote: >>>>>>>>>>>> The upload has failed repeatedly for me, so I'll clearly have = to find >>>>>>>>>>>> another way. >>>>>>>>>>>> Karl >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Nov 23, 2010 at 10:47 AM, Karl Wright wrote: >>>>>>>>>>>>> I'm uploading a release candidate now. =A0But someone needs t= o feed the >>>>>>>>>>>>> hamsters turning the wheels or something, because the upload = speed to >>>>>>>>>>>>> that machine is 51KB/sec, so it's going to take 3 hours to ge= t the >>>>>>>>>>>>> candidate up there, if my network connection doesn't bounce i= n the >>>>>>>>>>>>> interim. =A0Is there any other place available? >>>>>>>>>>>>> >>>>>>>>>>>>> Karl >>>>>>>>>>>>> >>>>>>>>>>>>> On Fri, Nov 19, 2010 at 8:34 AM, Grant Ingersoll wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Nov 19, 2010, at 6:18 AM, Karl Wright wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> I've created a signing key, and checked in a KEYS file. =A0= Apache >>>>>>>>>>>>>>> instructions for this are actually decent, so I didn't have= to make >>>>>>>>>>>>>>> much stuff up. =A0Glad about that. >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Yep, sorry, have been in meetings. >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Last remaining release issue is getting the release files t= o a >>>>>>>>>>>>>>> download mirror. =A0Maybe I can find some doc for that too. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Next steps would be to generate a candidate release which th= e rest of us can download. =A0Put it up on people.apache.org/~YOURUSERNAME/= ... and then send a note to the list saying where to locate it. =A0Rather t= han call a vote right away, just ask us to check it out and try it as there= will likely be issues for the first release. =A0Once we all feel we have a= decent candidate, we can call a vote, which should be a formality. >>>>>>>>>>>>>> >>>>>>>>>>>>>> See http://apache.org/dev/#releases for more info. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Karl >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Fri, Nov 19, 2010 at 4:13 AM, Karl Wright wrote: >>>>>>>>>>>>>>>> The build changes are complete. =A0I removed the modules l= evel from the >>>>>>>>>>>>>>>> hierarchy because it served no useful purpose and complica= ted matters. >>>>>>>>>>>>>>>> =A0The outer level build.xml now allows you build code, do= cs, and run >>>>>>>>>>>>>>>> tests separately from one another, and gives you help as a= default. >>>>>>>>>>>>>>>> "ant image" builds you the deliverable .zip and tar.gz fil= es. =A0Online >>>>>>>>>>>>>>>> site has been polished so that it now contains complete ja= vadoc, as >>>>>>>>>>>>>>>> does the built and delivered .zip and tar.gz's. =A0In shor= t, =A0we *could* >>>>>>>>>>>>>>>> actually do a release now, if only we had (and incorporate= d) the KEYS >>>>>>>>>>>>>>>> file I alluded to earlier, which I do not know how to buil= d or obtain. >>>>>>>>>>>>>>>> =A0I believe this needs to be both generated and registere= d. =A0The site >>>>>>>>>>>>>>>> also needs to refer to a download location/list of mirrors= before it >>>>>>>>>>>>>>>> could go out the door. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Help? Grant? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Karl >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Nov 17, 2010 at 9:50 PM, Karl Wright wrote: >>>>>>>>>>>>>>>>> Hearing nothing, went ahead and made the port of document= ation to the >>>>>>>>>>>>>>>>> site official. =A0I also now include the generated site i= n the release >>>>>>>>>>>>>>>>> tar.gz and .zip. >>>>>>>>>>>>>>>>> Issues still to address before release: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> (1) source tar.gz and zip in outer-level build.xml, which= I will try >>>>>>>>>>>>>>>>> to address shortly. >>>>>>>>>>>>>>>>> (2) vehicle for release downloads, and naming thereof. = =A0In short, >>>>>>>>>>>>>>>>> where do I put these things so people can download them?? >>>>>>>>>>>>>>>>> (3) Voting procedures for release. =A0I've seen this done= as a vote in >>>>>>>>>>>>>>>>> general@incubator.org - is that actually necessary? >>>>>>>>>>>>>>>>> (4) Release branch and tag. =A0Do we want both? =A0What i= s the correct >>>>>>>>>>>>>>>>> naming for each in apache? >>>>>>>>>>>>>>>>> (5) Legal requirements. =A0CHANGES.txt, LICENSE.txt, etc.= =A0Do these need >>>>>>>>>>>>>>>>> to be included in the release tar.gz, or just the source = tar.gz? =A0I >>>>>>>>>>>>>>>>> suspect both, but please confirm. =A0Also, if there is a = typical >>>>>>>>>>>>>>>>> organization of the release tar.gz in relation to the sou= rce tar.gz >>>>>>>>>>>>>>>>> this would be a good time to make that known. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>> Karl >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Tue, Nov 16, 2010 at 5:44 PM, Karl Wright wrote: >>>>>>>>>>>>>>>>>> What I've done here is taken all the pages that I origin= ally put in >>>>>>>>>>>>>>>>>> the Wiki, describing how to set up and run ManifoldCF, a= nd converted >>>>>>>>>>>>>>>>>> them to xdocs that are part of the ManifoldCF site. =A0T= hese documents >>>>>>>>>>>>>>>>>> have no user content other than stuff Grant or I added, = according to >>>>>>>>>>>>>>>>>> their logs, so I feel that is safe to do. =A0I've left t= he wiki pages >>>>>>>>>>>>>>>>>> around but am thinking we'll want them to go away at som= e point. =A0Not >>>>>>>>>>>>>>>>>> sure exactly what to do with all the user comments to th= em, however. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Is this a reasonable way to proceed? =A0We should avoid = using the wiki >>>>>>>>>>>>>>>>>> in the future for documentation, seems to me, but otherw= ise I can see >>>>>>>>>>>>>>>>>> no issues here. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Karl >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Tue, Nov 16, 2010 at 5:36 PM, Grant Ingersoll wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Nov 15, 2010, at 1:23 PM, Jack Krupansky wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I didn't mean to imply that the wiki needs to be physi= cally included in the release zip/tar, just that snapshotting and versionin= g of the wiki should be done, if feasible, so that a user who is on an olde= r release can still see the doc for that release. I am just thinking ahead = for future releases. So, 0.1 does not need this right now. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Right, and I'm saying that we can't include user genera= ted content in a release unless we have explicitly asked for permission on = it in the form of patches and then committed by a committer. =A0Since we do= n't lock down our wiki, we can't do it. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> -- Jack Krupansky >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> -----Original Message----- From: Grant Ingersoll >>>>>>>>>>>>>>>>>>>> Sent: Monday, November 15, 2010 10:23 AM >>>>>>>>>>>>>>>>>>>> To: connectors-dev@incubator.apache.org >>>>>>>>>>>>>>>>>>>> Subject: Re: Release? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On Nov 10, 2010, at 1:22 AM, Jack Krupansky wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> And the wiki doc is also part of the release. Does th= is stuff get a version/release as well? Presumably we want doc for currentl= y supported releases, and the doc can vary between releases. Can we easily = snapshot the wiki? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> You can't put Wiki in a release, as their is no way to= track whether the person has permission to donate it.. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Will we have nightly builds in place? I think a 0.1 c= an get released without a nightly build, but it would be nice to say that w= e also have a "rolling trunk release" which is just the latest build off tr= unk and the latest wiki/doc as well. So, some people may want the official = 0.1, but others may want to run straight from trunk/nightly build. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> -- Jack Krupansky >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> -----Original Message----- From: Karl Wright >>>>>>>>>>>>>>>>>>>>> Sent: Tuesday, November 09, 2010 1:56 PM >>>>>>>>>>>>>>>>>>>>> To: connectors-dev@incubator.apache.org >>>>>>>>>>>>>>>>>>>>> Subject: Re: Release? >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Proposal: =A0Release to consist of two things: tar an= d zip of a complete >>>>>>>>>>>>>>>>>>>>> source tree, and tar and zip of the modules/dist area= after the build. >>>>>>>>>>>>>>>>>>>>> The implied way people are to work with this is: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> - to use just the distribution, untar or unzip the di= stribution >>>>>>>>>>>>>>>>>>>>> zip/tar into a work area, and either use the multipro= cess version, or >>>>>>>>>>>>>>>>>>>>> the quickstart example. >>>>>>>>>>>>>>>>>>>>> - to add a connector, untar or unzip the source zip/t= ar into a work >>>>>>>>>>>>>>>>>>>>> area, and integrate your connector into the build. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Is this acceptable for a 0.1 release? >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Karl >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> On Tue, Nov 9, 2010 at 10:22 AM, Jack Krupansky >>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>> Oh, I wasn't intending to disparage the RSS or other= connectors, just giving >>>>>>>>>>>>>>>>>>>>>> my own priority list of "must haves." By all means, = the "well-supported" >>>>>>>>>>>>>>>>>>>>>> connector list should be whatever list you want to f= eel is appropriate and >>>>>>>>>>>>>>>>>>>>>> exclude only those where "we" feel that "we" would n= ot be able to provide >>>>>>>>>>>>>>>>>>>>>> sufficient support and assistance online. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> That's great that qBase is offering access. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> BTW, I was just thinking that maybe we should try to= keep logs of each >>>>>>>>>>>>>>>>>>>>>> connector type in action so that people have a refer= ence to consult when >>>>>>>>>>>>>>>>>>>>>> debugging their own connector-related problems. In o= ther words, what a >>>>>>>>>>>>>>>>>>>>>> successful connection session is supposed to look li= ke. So, have a test and >>>>>>>>>>>>>>>>>>>>>> its "reference" log. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> -- Jack Krupansky >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> -----Original Message----- From: Karl Wright >>>>>>>>>>>>>>>>>>>>>> Sent: Tuesday, November 09, 2010 9:46 AM >>>>>>>>>>>>>>>>>>>>>> To: connectors-dev@incubator.apache.org >>>>>>>>>>>>>>>>>>>>>> Subject: Re: Release? >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> If you can claim "well supported" for the web connec= tor, you certainly >>>>>>>>>>>>>>>>>>>>>> should be able to claim it for the RSS connector. = =A0You could also >>>>>>>>>>>>>>>>>>>>>> reasonably include the JDBC connector because it doe= s not require a >>>>>>>>>>>>>>>>>>>>>> proprietary system to test. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> But if your definition is that tests exist for all t= he "well >>>>>>>>>>>>>>>>>>>>>> supported" ones, somebody has some work to do. =A0I'= d like to see a plan >>>>>>>>>>>>>>>>>>>>>> on how we get from where we are now to a more compre= hensive set of >>>>>>>>>>>>>>>>>>>>>> tests. =A0I've gotten qBase to agree to let me have = access to their Q/A >>>>>>>>>>>>>>>>>>>>>> infrastructure (which used to be MetaCarta's), but t= hat's only going >>>>>>>>>>>>>>>>>>>>>> to be helpful for diagnosing problems and doing deve= lopment, not for >>>>>>>>>>>>>>>>>>>>>> automated tests that anyone can run. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Karl >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 9, 2010 at 9:38 AM, Jack Krupansky >>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> And one of the issues on the list should be to defi= ne the "well-supported" >>>>>>>>>>>>>>>>>>>>>>> connectors for 0.5 (or whatever) as opposed to the = "code is there and >>>>>>>>>>>>>>>>>>>>>>> thought to work, you are on your own for testing/su= pport" connectors. >>>>>>>>>>>>>>>>>>>>>>> Longer >>>>>>>>>>>>>>>>>>>>>>> term, "we" should get most/all connectors into the = well-supported >>>>>>>>>>>>>>>>>>>>>>> category, >>>>>>>>>>>>>>>>>>>>>>> but I wouldn't use that as the bar for even 1.0. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> My personal minimum "well-supported" connector list= for a 0.5 would be >>>>>>>>>>>>>>>>>>>>>>> file >>>>>>>>>>>>>>>>>>>>>>> system, web, and SharePoint*. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> * Oh... there is the issue of SharePoint 2010 or wh= atever the latest is, >>>>>>>>>>>>>>>>>>>>>>> but >>>>>>>>>>>>>>>>>>>>>>> current MCF support should be good enough for a 0.5= release, I think. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> (Got to keep up with Google Connectors!) >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> -- Jack Krupansky >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> -----Original Message----- From: Karl Wright >>>>>>>>>>>>>>>>>>>>>>> Sent: Tuesday, November 09, 2010 9:28 AM >>>>>>>>>>>>>>>>>>>>>>> To: connectors-dev@incubator.apache.org >>>>>>>>>>>>>>>>>>>>>>> Subject: Re: Release? >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> I'm in favor of a release. =A0I'm not sure, though,= what the release >>>>>>>>>>>>>>>>>>>>>>> parameters ought to be. =A0I think the minimum is t= hat we need to build >>>>>>>>>>>>>>>>>>>>>>> a release infrastructure and plan, set up a release= process, and >>>>>>>>>>>>>>>>>>>>>>> decide what the release packaging should look like = (zip's, tar's, >>>>>>>>>>>>>>>>>>>>>>> sources, deliverables) and where the javadoc will b= e published online. >>>>>>>>>>>>>>>>>>>>>>> (It's possible that we may, for instance, decide to= change the way >>>>>>>>>>>>>>>>>>>>>>> the ant build scripts work to make it easier for pe= ople to build the >>>>>>>>>>>>>>>>>>>>>>> proprietary connectors after the fact, for instance= . =A0Or we could >>>>>>>>>>>>>>>>>>>>>>> claim that the release is just the sources, either = way.) >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> After that, we need to figure out what tickets we s= till want done >>>>>>>>>>>>>>>>>>>>>>> before the release occurs. =A0I'd argue for more te= sting, and I'm also >>>>>>>>>>>>>>>>>>>>>>> trying to figure out issues pertaining to Documentu= m and FileNet, >>>>>>>>>>>>>>>>>>>>>>> because these connectors require sidecar processes = that are not well >>>>>>>>>>>>>>>>>>>>>>> supported in the example. =A0We could go substantia= lly beyond that, but >>>>>>>>>>>>>>>>>>>>>>> I agree with Jack that 0.1 would be useful if we on= ly get that far. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Thoughts? >>>>>>>>>>>>>>>>>>>>>>> Karl >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 9, 2010 at 8:58 AM, Jack Krupansky >>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> At least get a release 0.1 dry-run with code as-is= out ASAP to flush out >>>>>>>>>>>>>>>>>>>>>>>> release process issues. This would help to send ou= t a message to the rest >>>>>>>>>>>>>>>>>>>>>>>> of >>>>>>>>>>>>>>>>>>>>>>>> the world that MCF is an available product rather = than purely >>>>>>>>>>>>>>>>>>>>>>>> development/incubation. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Then come up with a list of issues that people str= ongly feel need to be >>>>>>>>>>>>>>>>>>>>>>>> resolved before a true, squeaky-clean 1.0 release.= Maybe that is the >>>>>>>>>>>>>>>>>>>>>>>> original list of tasks, including better testing, = but some >>>>>>>>>>>>>>>>>>>>>>>> review/decisions >>>>>>>>>>>>>>>>>>>>>>>> are probably needed. That will be the ultimate tar= get. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Then decide on a "close enough" subset of issues t= hat would constitute >>>>>>>>>>>>>>>>>>>>>>>> what >>>>>>>>>>>>>>>>>>>>>>>> people consider a "solid beta" and target that as = a release 0.5 and focus >>>>>>>>>>>>>>>>>>>>>>>> on >>>>>>>>>>>>>>>>>>>>>>>> that as the near-term target (after getting 0.1 ou= t ASAP.) I personally >>>>>>>>>>>>>>>>>>>>>>>> do >>>>>>>>>>>>>>>>>>>>>>>> not have any major issues on the top of my head th= at I would hold out as >>>>>>>>>>>>>>>>>>>>>>>> "blockers" for a 0.5. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Or, get 0.1 out and then move on to a 0.2, etc. on= a monthly/bi-monthly >>>>>>>>>>>>>>>>>>>>>>>> basis as progress is made. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> In short, get MCF as-is 0.1 out ASAP, have a very = short list for MCF 0.5 >>>>>>>>>>>>>>>>>>>>>>>> to >>>>>>>>>>>>>>>>>>>>>>>> get it out reasonably soon, and then revisit what = 1.0 really means versus >>>>>>>>>>>>>>>>>>>>>>>> 0.6, etc. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> -- Jack Krupansky >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> -----Original Message----- From: Grant Ingersoll >>>>>>>>>>>>>>>>>>>>>>>> Sent: Tuesday, November 09, 2010 8:38 AM >>>>>>>>>>>>>>>>>>>>>>>> To: connectors-dev@incubator.apache.org >>>>>>>>>>>>>>>>>>>>>>>> Subject: Release? >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Now that we have NTLM figured out and the Memex st= uff behind us, how do >>>>>>>>>>>>>>>>>>>>>>>> people feel about working towards a release? >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> -Grant >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> -------------------------- >>>>>>>>>>>>>>>>>>>> Grant Ingersoll >>>>>>>>>>>>>>>>>>>> http://www.lucidimagination.com >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -------------------------- >>>>>>>>>>>>>>>>>>> Grant Ingersoll >>>>>>>>>>>>>>>>>>> http://www.lucidimagination.com >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -------------------------- >>>>>>>>>>>>>> Grant Ingersoll >>>>>>>>>>>>>> http://www.lucidimagination.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -------------------------- >>>>>>>>>> Grant Ingersoll >>>>>>>>>> http://www.lucidimagination.com >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>> >>>>>>> -------------------------- >>>>>>> Grant Ingersoll >>>>>>> http://www.lucidimagination.com >>>>>>> >>>>>>> >>>>> >>>>> -------------------------- >>>>> Grant Ingersoll >>>>> http://www.lucidimagination.com >>>>> >>>>> >>>> >>> > > -------------------------- > Grant Ingersoll > http://www.lucidimagination.com/ > > Search the Lucene ecosystem docs using Solr/Lucene: > http://www.lucidimagination.com/search > >