[Tilesathome] tah submit policy

[Matthias Julius]

Stephan <osm at stephans-server.de> writes:

> Hi,
>
> I have a patch ready that fixes the problem of Osmosis running out of 
> memory and no possibility to specify a heap size for it.
>
> I added a config variable "JavaHeapSize" that can be used to override 
> the default value of 256M I thought was reasonable for a default.
>
> Is there a policy or some things to take special care of before submitting?
> As this is a bugfix and no experimental feature I thought about 
> submitting to stable (and unstable to keep in sync).
> I would adjust the config.defaults and the tilesathome.conf files.
>
> What about the version file for the auto-update?
>
> Any advice from experienced tah developers?

I don't think there is a hard policy.

But, I consider it good practice if every change goes to -dev first.
There it can be tested by others.  Right now there is not much going
on in -dev anyway.  So there should be nothing to prevent changes to
be merged into stable after a couple of days.

Of course, if the change is really trivial there is not much danger in
applying it directly to stable except than forgetting to also do it to
unstable.  Therefore, unless the fix is really urgent I would always
put it into -dev and merge it into stable a week or so later after
others had the chance to complain about it.

Matthias