On 12/22/06, MATHUS Baptiste <firstname.lastname@example.org> wrote:
> > This is one of the areas where there were specific changes
> > made in 1.1.9, and yes there is a bug. It is fixed in trunk.
> Perfect! Maybe I'll use the trunk in the meantime.
> Is your release process a heavy task? How do you plan releasing 2.0 ga?
> Publishing an alpha first, then beta, and so on until the kind of bug I'm
> encountering is all fixed or do you plan releasing something like 1.9.1
> 1.9.2 until directly a 2.0? (To sum up, I try and see when a correction
> could be released and so if I must seriously consider using the trunk soon
> Thank you very much for answering though. I was fearing the fact that I
> would be the only one having this problem because of a particular conf.
There is no formal process per se. In a sense all of the 1.1.x releases are
beta/release candidates. I try not to release anything where I know there
I can see that this problem is a nuisance, so I will do a release sooner
rather than later. The SVN devs are talking about getting 1.4.3 and that
has some fixes for crashes on Windows, so I'd like to see if that progresses
so that I do not have two releases in a short time. Likewise, I expect to
see SVNKit 1.1.1 soon.
If those things do not happen next week, I'll probably put out a release.
Received on Fri Dec 22 14:58:22 2006