On 2013-09-06 13:01, Daniel Stone wrote:
I notice in the FAQ that you recommend patches / bug fixes before
making any major changes to the source code, which I can fully
understand. How would we go about proposing design /
implementation changes to the H2 clustering code?
This mailing list is the right place to discuss any proposed changes.
Start with a brief breakdown of your requirements i.e. what you see as
broken or inadequate.
Please don't just post a proposed design. Without knowing what problems
you are trying to solve, we won't be able to judge the fitness of any
proposed change.
Would anyone with the authority be able to work with us for a
donation to the project to speed this process up?
I don't know of anyone off-hand. Myself and Thomas both have full time
jobs and family responsibilities.
Fair warning - we're not the fastest moving bunch around :-)
Sometimes it can take a couple of days before someone gets around to
replying, and large patches can take a week or more before someone finds
time to sit down and review it.
There is some commercial support available:
http://h2database.com/html/links.html#commercial_support
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
