That timeline seems fine to me. What I suggest is to create a new version in the DIRKRB JIRA, and start assigning issues that must be fixed by the first release to it. Other issues can leave the "fix for" version blank. >From what I've seen so far of the project, the following are essential:
a) Sort out not-yet-commons-ssl dependency (perhaps this could be left out altogether for the first release) b) Resolve all issues surrounding code copied into Kerby from other projects (I think I've seen a few comments that indicate this) c) Support UDP in the transport handlers d) More robust error handling in the transport handlers e) More extensive interop testing with other APIs/KDCs Colm. On Fri, Apr 24, 2015 at 11:49 AM, Zheng, Kai <kai.zh...@intel.com> wrote: > Thanks Colm for raising the question. > > > > From my point of view, many codes of the project are to be stabilized and > tested. I’m a little sad I can’t be on the project in good much time. In a > quick estimation, maybe in 2 months or so? Let’s see and try our best, > maybe in another month will leave us much clear and answer this question > well, J. How others would think? Thanks. > > > > Regards, > > Kai > > > > *From:* Colm O hEigeartaigh [mailto:cohei...@apache.org] > *Sent:* Friday, April 24, 2015 6:07 PM > *To:* Apache Directory Developers List > *Subject:* Kerby release > > > > When do we anticipate a first release of Apache Kerby? No pressure from my > side, just wondering what the timeline is. > > Colm. > > > > -- > > Colm O hEigeartaigh > > Talend Community Coder > http://coders.talend.com > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
