Agile Software Development Practice-release Process/release Plan

Introduced:

Because our development cycle is iterative, in sprint, how each sprint goes to the customer to say our results, then I need some new features for demo and release, or some bug fixing. Demo I do not discuss here, in general is deployed on the server and then run the next to meeting everyone to see, we are here to discuss and publish (release) Related Topics.

Implementation mode:

Topic 1: How do we let publishers know what our sprint does? Because, like the JDK, its big release and small releases have some commentary to explain what features they have released this time, or what amendments we have, as we have done:

At the end of each sprint, if there is any change to the item (functional change/correction), a release note is added to the project.

The practice is that we use Maven-site-plugin, and then each time we update the site folder and add an entry in Site.xml to release notes:

Then we add a apt file and add the release notes

Now that we have MVN site, we can display the release notes we've written.