juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Viens, Steve" <Stephen.Vi...@FMR.COM>
Subject RE: LDAP DataStore/Authenticator code
Date Thu, 20 May 2004 18:29:56 GMT
Vijay, 

I haven't run your contribution yet but I have looked through it quite a
bit and I don't see why we wouldn't go ahead with this.  I've got some
concern about possible copyright issues related to this contribution so
we'll have to work through those together.

There have been some changes to the code base since you posted this - my
fault for taking so long - but they'll have to be ironed out. We'll also
need to look over the changes you made to jUDDI's SaveXxxx functions to
make sure the change doesn't cause problems for the JDBC DataStore. Last
thing is that I'd like to recommend some changes to the way the
contribution is packaged.

Also, we haven't discussed this but can I assume that you would be
interested in joining the project as a committer to help support the
LDAP implementation.

Steve

-----Original Message-----
From: Vijay KN [mailto:KNVIJAY@novell.com] 
Sent: Tuesday, May 18, 2004 5:04 AM
To: Viens, Steve
Subject: LDAP DataStore/Authenticator code


Hi Steve,

Checking to see if you had a chance to go over the LDAP
DataStore/Authenticator code.

Let me know if you need anything.

regards
Vijay

>>> Stephen.Viens@FMR.COM 4/15/2004 8:18:08 PM >>>
I volunteer. 

I have recently started looking over Vijay's LDAP
DataStore/Authenticator contribution but this is more pressing I
think.
How about starting with a 0.9rc1 (Release Candidate 1) and work our
way
to 0.9 final?  Labeling with each release candidate?

Halting code changes is a good idea. 

I think we need more documentation and that doc should be included
with
the release's docs folder (as it has been in the past).  Perhaps
replacing what's currently in the docs folder with a copy of the jUDDI
web site (the old juddi.org web site is in there now). That seems to
be
the typical way to go with other Apache products.

Steve

-----Original Message-----
From: Andy Cutright [mailto:Andy.Cutright@borland.com] 
Sent: Wednesday, April 14, 2004 1:42 PM
To: juddi-dev@ws.apache.org 
Subject: RE: time to organize a new release? 


i've heard someone say "initiative is punished" .. i'm kinda deep in
the
subscription API stuff ;) anyone want to volunteer to be release
manager? 

we can toss the process up on the wiki as we define it, and then
transfer it to the website .. i've already created some keys to sign
the
release, those are checked in last time i checked. 

some initial proposed relase steps

0. i would like the the UDDI4J test suite run prior to release.
currently there's one broken test, and i'm willing to live with that. 
0.5 any other test suites? 
1. temporarily halt any code chages while doing a release candidate
2. apply a label for each candidate
3. post it up somewhere

cheers,
andy 

> -----Original Message-----
> From: Viens, Steve [mailto:Stephen.Viens@FMR.COM] 
> Sent: Wednesday, April 14, 2004 4:46 AM
> To: juddi-dev@ws.apache.org 
> Subject: RE: time to organize a new release? 
> 
> I agree completely. Would be nice to release something under 
> Apache too.
> 
> Steve
> 
> Steve Viens
> Fidelity Center for Applied Technology
> Open Source Support Center
> http://opensource.fmr.com 
> 617.392.0496 (phone) 
> 617.385.1954 (fax)
> 
> -----Original Message-----
> From: Andy Cutright [mailto:Andy.Cutright@borland.com] 
> Sent: Tuesday, April 13, 2004 5:12 PM
> To: juddi-dev@ws.apache.org 
> Subject: time to organize a new release? 
> 
> 
> hi all, 
> 
> we've got a lot of user folks running old code with known 
> bugs. it'd be
> nice if we could provide them a binary drop. we're outta the 
> incubator,
> so we're free to do so.. thoughts?
> 
> cheers,
> andy 
> 
> 

Mime
View raw message