Hi Werner,
I didn't want to force you fixing my bugs. My software now is running with the current Castor version, so it is not very time critical to fix the bugs. It was only of my interest to know how the issues are scheduled, because in Jira I saw hundrets of unresolved ones, which making me pessimistic that my issues will be take into account in a manageable time. I know, of course, that Castor is an open source software. So for the reporting of my bugs I did some efforts as the extracting of the essence of the bugs to give a very simple example as well as the writing of a JUnit-TestCase documenting clearly what is going wrong. At the last I want to thank you very much for managing and enhancing Castor voluntarily. It is a very useful tool which comes in work in many of my projects, so I dont want to miss it. Best Regards /Roman Klähne Werner Guttmann schrieb: > Hi Roman, > > as already stated in our original conversation, these bugs will be > addressed once release 1.3 has been made available. As disappointing > this might be for you in this case, I simply shall not delay the > imminent release of Castor 1.3 indefinitely because of new issues. > > In terms of scheduling of bugs, please have a look at our Jira instance > available at > > http://jira.codehaus.org/browse/CASTOR > > to get an idea about (maintenance) releases planned in the immediate > future (after 1.3 GA), especially release 1.3.1 and 1.3.2. In general, > it's up to us (committers) to assess bugs, prioritise them and provide > patches (according to various criteria). > > As always, there's ways to decrease the time it take to have a bug > fixed, incl. > > a) voting > b) providing detailed problem analysis, incl. e.g. identifying areas of > problems in source code > c) providing (initial) patches for review. > d) providing fully tested patches, incl. e.g. JUnit test cases > e) providing fully tested patches, incl. JUnit test cases *and* CTF > integration tests, and finally > f) taking up professional services. > > I think I don't have to repeat that this is an open source project, > whose quality and liveliness depends on its community, incl. you > (amongst others). If you are looking for professional response levels > (similar to commercial offerings) without your help/involvement in the > spirit of open source development, please do consider taking up > professional support (where I and others will be able to assist you and > meet your requirements/deadlines according to your needs). > > Sorry for (re)iterating this quite strongly, but being an open source > committer, who invests a great deal of his spare (unpaid) time into the > development and enhancement of Castor, implies that we have to manage > expectations. > > Regards > Werner > Roman Klaehne wrote: >> Hi Werner, >> >> >> I've reported two bugs (2618, 2617) recently. What is your plan for >> fixing these bugs or rather how you are scheduling the bugs in general? >> >> Best Regards >> /Roman Klaehne >> >> >> Werner Guttmann schrieb: >>> Hello, >>> >>> for those of you wondering about the release plans for Castor, this is >>> just to let you know that I am about three or four issues away from >>> making Castor 1.3 GA available. For those interested in what's to be >>> resolved before the imminent release, please browse to >>> >>> http://jira.codehaus.org/browse/CASTOR >>> >>> and have a look at the 1.3 release tag. >>> >>> Any comments would be appreciated. >>> >>> Regards >>> Werner Guttmann >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
