Jan Schulz wrote:
Just a question: Is it ok if a policy package is that openly available for changes?
It's not open for changes just because it is co-maintained. The java-common mainitainers just write down the decisions that are made by the debian-java list. Just like it's done on debian-policy.
BTW, what is actually the latest (and greatest) java policy? Almost everything I've found during the last days seems outdated for years (woody as 'testing', jdk1.3 as 'latest JDK' and so on).
It's the one in java-common 0.21, uploaded today.
BTW, can you post you suggestion already now, so I can try to addapt my package to the 'new way' (assuming, that the only change isn't autobuild related...).
I'd like to implement and test my improvements in some packages first before suggesting them for policy. This way, I know that they really work and can be implemented easily.
Stefan