Hi all,
Looking at the very empty result of the announcement plugin, I was wondering if we as the development team of wicket should improve our development process a little.
I propose that new features, changes to existing components, api-changes, and the like are first reported on the sourceforge.net RFE trackers, in order to keep track of the changes. When a feature/change/etc. is ready and integrated into the CVS trunk, the item can be closed and marked for the next release. The item should also be added to the document 'Wicket/xdocs/changes.xml', so that when a new release is built, the announcement can be automatically generated. Also, the changes.html page will show all items per release.
Any comments?
Martijn Dashorst
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Wicket-develop mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/wicket-develop
