First of all: Joern, thanks for the spring cleaning :)
Joern Nettingsmeier schrieb: [...] >> +1 to merge, but merge the whole structure. +1, but IMO we shouldn't include the human-readable information directly. We should add a link to a readme.xml, like Joern proposed later on. > the whole structure cannot be merged iiuc. publication.xconf is a > Configurable data file, and the Configurable interface supports only a > subset of XML - notably, mixed content is not supported, which would be > natural for a "readme" section. Well, if the technology doesn't support our needs, we should either use a different configuration mechanism or refine the configuration (see above). -- Andreas > > therefore my current approach is to allow only simple fields in > publication.xconf. > > i'm also thinking of providing a global "readme.xml" that is called via > fallback. it can be used by developers to inform users about important > changes and required tweaks, and publications could override it to add > their own information. > >>> lazy consensus in effect ;) >> >> based on what definition? I mean about many days are we talking? What >> about weekend, business days, people on vacation? >> >> I think it's important to get this straight, otherwise it's just >> meaningless > > note the smiley. i was grinning because i anticipated the usual > situation: /me starts hacking frantically, and everybody else is out of > office until monday... > it is not my intention to sneak something in without proper review and > discussion. > i'll post a patch for you to review before anything will be committed. > at the moment, the patch is at 557 lines out, 258 lines in, with a > slight gain in functionality (which is how i like things to be ;) > > regards, > > jörn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
