Re: [Exist-open] Bugtracker

[Ralf J. <ral...@gm...>]

Hi,

> I think it is best to do both: post the issue to the tracker for
> reference and to the list to bring it to the attention of those not
> following the tracker. It also helps to remind us of important issues
> or patches ;-)
I explicitly did not do that as I considered it rude to draw the attention to 
my issue that loudly - so thanks for telling me that this is actually desired 
:)

> And finally, we do not have huge requirements before
> giving commit rights to new developers. If you think a patch is very
> important and should really be applied soon, do not hesitate to ask if
> you can apply it yourself. I'm always happy about help.
Well, I think those patches and test cases I mentioned are rather easy and 
could go in unmodified. The patches are not critical though, and the test cases 
obviously don't help anyone, except for precisely documenting the issue.
The problem is that exist has a huge codebase and I use only a small fraction 
of it - and I do not understand the overall architecture, I merely "grep" 
through the sourcecode until I find what I want, or give up ;-) . So, I fear if 
I submit the more complicated patches, I will break something without even 
knowing or understanding what happens. Which is why I usually post them on the 
mailing-list and hope for feedback. However I understand you got a large to-do 
list and some more serious issues before 1.5 gets into polishing phase.
I am queuing most of the patches on my local git-svn clone anyway, so I can 
easily re-send them once exist is more stable.

Thanks for your response,
Ralf