Make a tag from the release branch, not the develop branch. Develop branch could have changes that were made while the release was being prepared. After merging the release to develop it could be different than what is being released from the release branch. You can see the diagram for the nvie model here: http://nvie.com/posts/a-successful-git-branching-model/
-Omar On Thursday, December 27, 2012, Justin Mclean wrote: > Hi, > > Still to do: > 1. Place release in correct location ie /dist not /dist/incubation (OK > for now I think) > 2. Official announcement to various lists > 3. Sync release branch to production > 4. Tag trunk with "Apache Flex 4.9.0" > > Have I forgotten anything? > > Currently 3 is broken for some reason (SSL handshake error) so I can't do > 4, should I just tag the release in develop instead? (and merge that tag > with trunk at a later date when we can?) > > Thanks, > Justin