Arttu Manninen schrieb:
Tarjei wrote:
What would be smart is if we moved the CHANGES file to xml and then had
some phing commands to manipulate it so that when you do phing package
they just get included as the changelog entries in package.xml. Also,
phing package should have an extra comment usage for adding an extra
comment when uploading the file.

Is there some big reason for XML changelog? The current simple textual
presentation is very human-readable and machine-readable.

My biggest wish:
Commandline upload of new releases.

Should be very doable.



My biggest wish (apart from all the above, of course :-): More robustness in the Install Pear Packages script in datagard. Some days ago I did an installation on a freshly-installed Debian Testing system with no strange PHP settings, and it produced lots of errors, which caused quite a few packages not to be installed. datamanager2 installation didn't work because it needs more memory than the default configuration of Debian offers and for some reason, the static files from all components failed to install. When I manually installed everything following a blog post by Piotras, it worked (after increasing pear's memory_limit), but the standard installation doesn't provide a working midcom


Bye,

Andreas
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user

Reply via email to