Return-Path: Delivered-To: apmail-incubator-connectors-dev-archive@minotaur.apache.org Received: (qmail 25369 invoked from network); 6 Dec 2010 13:56:20 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 Dec 2010 13:56:20 -0000 Received: (qmail 83318 invoked by uid 500); 6 Dec 2010 13:56:20 -0000 Delivered-To: apmail-incubator-connectors-dev-archive@incubator.apache.org Received: (qmail 83231 invoked by uid 500); 6 Dec 2010 13:56:18 -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 83223 invoked by uid 99); 6 Dec 2010 13:56:17 -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 13:56:17 +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.182 as permitted sender) Received: from [209.85.216.182] (HELO mail-qy0-f182.google.com) (209.85.216.182) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Dec 2010 13:56:12 +0000 Received: by qyk36 with SMTP id 36so9040051qyk.6 for ; Mon, 06 Dec 2010 05:55:51 -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=8zRz10FKBUV3hZuzVG6iq9Lya8mYAfFBIP+aqL5g43k=; b=xj45bjNE9A0oWMuBnJoZa8Wr/ERgSJFYa15LQMj0wGsS8WwGOS4UcQcxf2DGkkThwu 09t4lqhSmHp/1n4oLErKBZkYOgC+7LdTWvzJi0as2bajS6409juiaZAuE9gU/qDefSuH d52g5GDbVBU/83w5iXywXYgPIVR6fE+1px3Bs= 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=rcFl0eRGSqkDFWO7T1hu3A46VruagI/BFXRXjSPzbIBLxTSyUoOiAbPLixZhG3n1us z7V9YBeqfGXh7ZxaxvDnyAmrR4VNANvkoOfyxSYSHJNwli/GhRad684I/NEI0RWHG/2A rwxPwQ8ELrW+O16YQ4c+KI3h9Hg8KP2oSeZWM= MIME-Version: 1.0 Received: by 10.229.241.194 with SMTP id lf2mr4436650qcb.164.1291643751673; Mon, 06 Dec 2010 05:55:51 -0800 (PST) Received: by 10.229.85.70 with HTTP; Mon, 6 Dec 2010 05:55:51 -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 08:55:51 -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 ... 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 wr= ote: >>> >>> On Dec 2, 2010, at 9:54 PM, Karl Wright wrote: >>> >>>> Hi Grant, >>>> >>>> In offline conversation you clarified that for (1) you are looking for >>>> 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 trunk >>>> (e.g. CHANGES.txt). =A0Are you envisioning that we make these specific >>>> changes in the release branch only? >>> >>> It's perfectly fine for CHANGES.txt to be on trunk. =A0You make the cha= nge 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 stuff,= but for now let's just assume trunk is under code freeze and the only chan= ges 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 did = get it to compile. >>>>> >>>>> Notes: >>>>> >>>>> 1. We should package the stuff all under apache-manifold-0.1 so that = 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 o= f the LICENSE.txt file (See Solr's for instance) >>>>> 4. The CHANGES.txt file should reflect that it is a release and not t= runk (not critical to fix) >>>>> 5. Is there anyway to make the package smaller? =A0Maybe we don't nee= d 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 other= places. >>>>> 8. We should hook in RAT (see Solr's build file) to verify that all s= ource 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 wro= te: >>>>>>> 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 ge= t to /x1/home/kwright >>>>>>>> >>>>>>>> FWIW, if you have a public_html directory in your directory and th= en place the files there, everyone can download them and check them out at = 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:5= 7 manifoldcf-0.1.tar.gz.md5 >>>>>>>>> -rw-r--r-- =A01 kwright =A0kwright =A0 =A0 =A0 =A0 60 Nov 23 17:5= 7 manifoldcf-0.1.zip.md5 >>>>>>>>> -rw-r--r-- =A01 kwright =A0kwright =A0158734230 Nov 23 17:55 mani= foldcf-0.1.zip >>>>>>>>> -rw-r--r-- =A01 kwright =A0kwright =A0156742315 Nov 23 17:06 mani= foldcf-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 to = feed the >>>>>>>>>>> hamsters turning the wheels or something, because the upload sp= eed to >>>>>>>>>>> that machine is 51KB/sec, so it's going to take 3 hours to get = the >>>>>>>>>>> candidate up there, if my network connection doesn't bounce in = 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. =A0Ap= ache >>>>>>>>>>>>> instructions for this are actually decent, so I didn't have t= o make >>>>>>>>>>>>> much stuff up. =A0Glad about that. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Yep, sorry, have been in meetings. >>>>>>>>>>>> >>>>>>>>>>>>> Last remaining release issue is getting the release files to = a >>>>>>>>>>>>> download mirror. =A0Maybe I can find some doc for that too. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Next steps would be to generate a candidate release which the = 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 tha= n call a vote right away, just ask us to check it out and try it as there w= ill likely be issues for the first release. =A0Once we all feel we have a d= ecent 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 lev= el from the >>>>>>>>>>>>>> hierarchy because it served no useful purpose and complicate= d matters. >>>>>>>>>>>>>> =A0The outer level build.xml now allows you build code, docs= , and run >>>>>>>>>>>>>> tests separately from one another, and gives you help as a d= efault. >>>>>>>>>>>>>> "ant image" builds you the deliverable .zip and tar.gz files= . =A0Online >>>>>>>>>>>>>> site has been polished so that it now contains complete java= doc, as >>>>>>>>>>>>>> does the built and delivered .zip and tar.gz's. =A0In short,= =A0we *could* >>>>>>>>>>>>>> actually do a release now, if only we had (and incorporated)= the KEYS >>>>>>>>>>>>>> file I alluded to earlier, which I do not know how to build = or obtain. >>>>>>>>>>>>>> =A0I believe this needs to be both generated and registered.= =A0The site >>>>>>>>>>>>>> also needs to refer to a download location/list of mirrors b= efore 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 documentat= ion to the >>>>>>>>>>>>>>> site official. =A0I also now include the generated site in = 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. =A0I= n short, >>>>>>>>>>>>>>> where do I put these things so people can download them?? >>>>>>>>>>>>>>> (3) Voting procedures for release. =A0I've seen this done a= s a vote in >>>>>>>>>>>>>>> general@incubator.org - is that actually necessary? >>>>>>>>>>>>>>> (4) Release branch and tag. =A0Do we want both? =A0What is = 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 ta= r.gz? =A0I >>>>>>>>>>>>>>> suspect both, but please confirm. =A0Also, if there is a ty= pical >>>>>>>>>>>>>>> organization of the release tar.gz in relation to the sourc= e 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 original= ly put in >>>>>>>>>>>>>>>> the Wiki, describing how to set up and run ManifoldCF, and= converted >>>>>>>>>>>>>>>> them to xdocs that are part of the ManifoldCF site. =A0The= se documents >>>>>>>>>>>>>>>> have no user content other than stuff Grant or I added, ac= cording to >>>>>>>>>>>>>>>> their logs, so I feel that is safe to do. =A0I've left the= wiki pages >>>>>>>>>>>>>>>> around but am thinking we'll want them to go away at some = point. =A0Not >>>>>>>>>>>>>>>> sure exactly what to do with all the user comments to them= , however. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Is this a reasonable way to proceed? =A0We should avoid us= ing the wiki >>>>>>>>>>>>>>>> in the future for documentation, seems to me, but otherwis= e 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 physica= lly included in the release zip/tar, just that snapshotting and versioning = of the wiki should be done, if feasible, so that a user who is on an older = release can still see the doc for that release. I am just thinking ahead fo= r future releases. So, 0.1 does not need this right now. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Right, and I'm saying that we can't include user generate= d 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 don'= 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 this= stuff get a version/release as well? Presumably we want doc for currently = supported releases, and the doc can vary between releases. Can we easily sn= apshot the wiki? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> You can't put Wiki in a release, as their is no way to t= rack whether the person has permission to donate it.. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Will we have nightly builds in place? I think a 0.1 can= get released without a nightly build, but it would be nice to say that we = also have a "rolling trunk release" which is just the latest build off trun= k 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 and = zip of a complete >>>>>>>>>>>>>>>>>>> source tree, and tar and zip of the modules/dist area a= fter the build. >>>>>>>>>>>>>>>>>>> The implied way people are to work with this is: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> - to use just the distribution, untar or unzip the dist= ribution >>>>>>>>>>>>>>>>>>> zip/tar into a work area, and either use the multiproce= ss version, or >>>>>>>>>>>>>>>>>>> the quickstart example. >>>>>>>>>>>>>>>>>>> - to add a connector, untar or unzip the source zip/tar= 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 c= onnectors, just giving >>>>>>>>>>>>>>>>>>>> my own priority list of "must haves." By all means, th= e "well-supported" >>>>>>>>>>>>>>>>>>>> connector list should be whatever list you want to fee= l is appropriate and >>>>>>>>>>>>>>>>>>>> exclude only those where "we" feel that "we" would not= 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 k= eep logs of each >>>>>>>>>>>>>>>>>>>> connector type in action so that people have a referen= ce to consult when >>>>>>>>>>>>>>>>>>>> debugging their own connector-related problems. In oth= er words, what a >>>>>>>>>>>>>>>>>>>> successful connection session is supposed to look like= . 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 connecto= r, you certainly >>>>>>>>>>>>>>>>>>>> should be able to claim it for the RSS connector. =A0Y= ou could also >>>>>>>>>>>>>>>>>>>> reasonably include the JDBC connector because it does = not require a >>>>>>>>>>>>>>>>>>>> proprietary system to test. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> But if your definition is that tests exist for all the= "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 comprehe= nsive set of >>>>>>>>>>>>>>>>>>>> tests. =A0I've gotten qBase to agree to let me have ac= cess to their Q/A >>>>>>>>>>>>>>>>>>>> infrastructure (which used to be MetaCarta's), but tha= t's only going >>>>>>>>>>>>>>>>>>>> to be helpful for diagnosing problems and doing develo= pment, 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 define= the "well-supported" >>>>>>>>>>>>>>>>>>>>> connectors for 0.5 (or whatever) as opposed to the "c= ode is there and >>>>>>>>>>>>>>>>>>>>> thought to work, you are on your own for testing/supp= ort" connectors. >>>>>>>>>>>>>>>>>>>>> Longer >>>>>>>>>>>>>>>>>>>>> term, "we" should get most/all connectors into the we= ll-supported >>>>>>>>>>>>>>>>>>>>> category, >>>>>>>>>>>>>>>>>>>>> but I wouldn't use that as the bar for even 1.0. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> My personal minimum "well-supported" connector list f= or a 0.5 would be >>>>>>>>>>>>>>>>>>>>> file >>>>>>>>>>>>>>>>>>>>> system, web, and SharePoint*. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> * Oh... there is the issue of SharePoint 2010 or what= ever the latest is, >>>>>>>>>>>>>>>>>>>>> but >>>>>>>>>>>>>>>>>>>>> current MCF support should be good enough for a 0.5 r= elease, 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, w= hat the release >>>>>>>>>>>>>>>>>>>>> parameters ought to be. =A0I think the minimum is tha= t we need to build >>>>>>>>>>>>>>>>>>>>> a release infrastructure and plan, set up a release p= rocess, and >>>>>>>>>>>>>>>>>>>>> decide what the release packaging should look like (z= ip's, tar's, >>>>>>>>>>>>>>>>>>>>> sources, deliverables) and where the javadoc will be = published online. >>>>>>>>>>>>>>>>>>>>> (It's possible that we may, for instance, decide to c= hange the way >>>>>>>>>>>>>>>>>>>>> the ant build scripts work to make it easier for peop= le to build the >>>>>>>>>>>>>>>>>>>>> proprietary connectors after the fact, for instance. = =A0Or we could >>>>>>>>>>>>>>>>>>>>> claim that the release is just the sources, either wa= y.) >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> After that, we need to figure out what tickets we sti= ll want done >>>>>>>>>>>>>>>>>>>>> before the release occurs. =A0I'd argue for more test= ing, and I'm also >>>>>>>>>>>>>>>>>>>>> trying to figure out issues pertaining to Documentum = and FileNet, >>>>>>>>>>>>>>>>>>>>> because these connectors require sidecar processes th= at are not well >>>>>>>>>>>>>>>>>>>>> supported in the example. =A0We could go substantiall= y beyond that, but >>>>>>>>>>>>>>>>>>>>> I agree with Jack that 0.1 would be useful if we only= 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 o= ut ASAP to flush out >>>>>>>>>>>>>>>>>>>>>> release process issues. This would help to send out = a message to the rest >>>>>>>>>>>>>>>>>>>>>> of >>>>>>>>>>>>>>>>>>>>>> the world that MCF is an available product rather th= an purely >>>>>>>>>>>>>>>>>>>>>> development/incubation. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Then come up with a list of issues that people stron= gly feel need to be >>>>>>>>>>>>>>>>>>>>>> resolved before a true, squeaky-clean 1.0 release. M= aybe that is the >>>>>>>>>>>>>>>>>>>>>> original list of tasks, including better testing, bu= t some >>>>>>>>>>>>>>>>>>>>>> review/decisions >>>>>>>>>>>>>>>>>>>>>> are probably needed. That will be the ultimate targe= t. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Then decide on a "close enough" subset of issues tha= t 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 out = ASAP.) I personally >>>>>>>>>>>>>>>>>>>>>> do >>>>>>>>>>>>>>>>>>>>>> not have any major issues on the top of my head that= 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 sh= ort 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 stuf= f 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 >>> >>> >> >