<commit_before>===================================
Sofia-SIP release management README
===================================

:Author: <NAME> <kai -dot vehmanen -at- nokia -dot- com>
:Version: 20060504-9
:Formatting: reStructuredText, http://docutils.sourceforge.net/rst.html

Introduction
============

This README contains instructions for making new Sofia-SIP releases.

Links to other resources
========================

sofia-sip/README.developers

The release notes
=================

The release notes should contain the following sections:

- about Sofia-SIP
    - copied verbatim from sofia-sip/README
- list of changes since last release
    - maintained in sofia-sip/RELEASE
    - see diff between cvs/darcs between previous and
      this version
    - written in freshmeat.net "Changes:" style 
- notes on API/ABI interface changes 
    - maintained in sofia-sip/RELEASE
    - all changes in public interfaces, plus other
      notes that developers should be aware of
- contributors to this release
    - maintained in sofia-sip/RELEASE
    - also sofia-sip/AUTHORS should be updated (file
      should list all persons/companies who have code/scripts/etc
      copyrighted to them in the sofia-sip tree)

See the RELEASE.template file for a full list of release note
sections.

Making the release tarball 
==========================

- update the version number in sofia-sip/configure.ac
- make sure everything that is supposed to be in the
  release is in the master darcs tree
- run 'make distcheck' (requires automake-1.7 or newer)
- tag repos (darcs and any slave trees) with release tag
  'rel-sofia-sip-x_y_z', where x_y_z is the version number (see
  README.developers):

  darcs tag -m"rel-sofia-sip-x_y_z"
  cvs tag rel-sofia-sip-x_y_z

- calculate md5 and sha1 hashes using md5sum and sha1sum utils,
  and copy the values to the release-notes (see below)

Creating the release notes and updating the website
===================================================

- combine the sofia-sip/RELEASE contents with
  the template found from sfnet_www/templates/relnotes.txt
- store the resulting release notes to 
  sfnet_www/relnotes/relnotes-sofia-sip-x.y.z.txt
- add explicit link to the release notes to <commit_msg>Update release process based on 1.11.9 lessons learned.<commit_after>===================================
Sofia-SIP release management README
===================================

:Author: <NAME> <kai -dot vehmanen -at- nokia -dot- com>
:Version: 20060601-10
:Formatting: reStructuredText, http://docutils.sourceforge.net/rst.html

Introduction
============

This README contains instructions for making new Sofia-SIP releases.

Links to other resources
========================

sofia-sip/README.developers

The release notes
=================

The release notes should contain the following sections:

- about Sofia-SIP
    - copied verbatim from sofia-sip/README
- list of changes since last release
    - maintained in sofia-sip/RELEASE
    - see diff between cvs/darcs between previous and
      this version
    - written in freshmeat.net "Changes:" style 
- notes on API/ABI interface changes 
    - maintained in sofia-sip/RELEASE
    - all changes in public interfaces, plus other
      notes that developers should be aware of
- contributors to this release
    - maintained in sofia-sip/RELEASE
    - also sofia-sip/AUTHORS should be updated (file
      should list all persons/companies who have code/scripts/etc
      copyrighted to them in the sofia-sip tree)

See the RELEASE.template file for a full list of release note
sections.

Making the release tarball 
==========================

- update the version number in sofia-sip/configure.ac
- make sure everything that is supposed to be in the
  release is in the master darcs tree
- run 'make distcheck' to verify everything is ready for
  release (requires automake-1.7 or newer)
- tag repos (darcs and any slave trees) with release tag
  'rel-sofia-sip-x_y_z', where x_y_z is the version number (see
  README.developers):
    sh> darcs tag -m"rel-sofia-sip-x_y_z"
    sh> cvs tag rel-sofia-sip-x_y_z
- take a fresh checkout of the release using the release tag
- create the release tarbaal with "make distcheck"
- calculate md5 and sha1 hashes using md5sum and sha1sum utils,
  and copy the values to the release-notes (see below)

Creating the release notes and updating the website
===================================================

- combine the sofia-sip/RELEASE contents with
  the template found from sfnet_www/templates/relnotes.txt
- store the resulting release notes to 
  sfnet_www/relnotes/relnotes-sofia-sip-x.y.z.txt
- add explicit link to the release notes to 
{'fraction_non_alphanumeric': 0.14169694379140843, 'fraction_numerical': 0.007480230818550973, 'mean_word_length': 3.9367088607594938, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 9, 'https://': 0, 'lorem ipsum': 0, 'www.': 4, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6583357', 'n_tokens_mistral': 1405, 'n_tokens_neox': 1349, 'n_words': 526}