> > Is there any information on the steps to release a project and how to > handle dependencies on other projects >
We spoke about how we would use the trunk and svn:externals a while back, so that the trunk would contain pointers to the current released version of each project. Obviously projects that depend on others will have to release at the same time or after their dependants. Some steps to release a project would be useful. We probably need a list of steps which would include: - Build the release build locally??? - Tag revision - Get the binaries (and docs) uploaded to the site in a zip with dependencies - Update the website - Announce it on the mailing lists Do we want a page on the Castle site where it lists all the projects with their current version and next version status? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
