Versions Compared

Old Version 13

changes.mady.by.user haleh mahbod

Saved on

compared with

New Version 14

changes.mady.by.user Luciano Resende

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This is work in progress. At this point, thoughts are put together to review with the community. Please help to complete this

What's a Release

The ASF release definition basically says that any artifact that is made available for people outside of the Apache Tuscany project is considered a release. The Release process usually consist of preparing the contents of the release on the project dev-list, voting release candidate(s) and, because Tuscany is still under Incubation, asking the iPMC to approve the release after it has already been approved on the project development community.

Prerequisites

DAS releases are dependent on SDO release. Make sure we have a SDO release to base this release on.

...

  1. Declare a candidate build and ask for feedback on devlist and user list. Work out any issues that are voiced.
  2. Get some to verify that all of the samples pass without issues. Integration tests and unit tests should run and known problems need to be identifed.
  3. Initiate a vote on tuscany-dev mailing list for the release candidate to make the build a public release.
  4. After 3 days, post the result to the devlist
  5. Once the community approved the candidate, create a tag from the branch (or trunk if no branch)
    1. Note that a release must have a referenceable tag
      (lightbulb) svn will complain when you try to do an svn commit into a tag, which is a warning only, and during this phase of the release process, updates to a tag are justifiable
  6. Get approval from IPMC to make this a public release. Send a note to general@apache.org which summarizes the result of vote on devlist and include a pointer to the release in your note. 3 (+1) IPMC votes are required to make this a public release and of course no (-1).
  7. Once you have IPMC approval, post the release to people.apache.org.
  8. Update the version elements of the poms to define the version of the parent pom and buildtools that should be used
  9. Update the tags version names of the distributable artifacts to non SNAPSHOT titles that match the release name
  10. Update the tags version names of the dependencies to non SNAPSHOT versions, if not already done earlier in the release candidate process
  11. Ideally update the tags version names of maven plugins to non SNAPSHOT versions if not already done earlier in the release candidate process (note that if the plugin behaviour changes after release, your tag or source distribution may not build in the same way as it did when you released if you rely on SNAPSHOT plugin versions)
  12. Rebuild and upload a new release to /www/people.apache.org/dist/incubator/tuscany/java
  13. update 'Download' link on the wiki and make it a goal to update or add documentation.
  14. Announce the release by sending to anounce@apache.org (note that you must use an apache.org email address to do this), copying tuscany-dev, tuscany-user and general@incubator
  15. Don't forget that all this could not have been done without everyone's help. Post a congratulation note to the dev list and thank the entire team for their efforts to make this happen (smile) And thank you for the extra ordinary effort to make this happen (smile)

Good References

...