Kondor+ Adaptor Release Process

==========Release Process===========


1. get all of the deliverables such as
   * K+ Adaptor binary by autobuild tool. svn version number should be identified.

hudson :/export/home/javadev/remote/remote/workspace/KondorPlusLBN/trunk/L:/Source_Archive/kondorPlusLBN/release

check svn number in hardson entries file should be same with the latest svn version number

   * Install guide

2. verify the functionality and reports

   * basic integration test should be done on both solaris( and windows - optional).

   * basic test on the new functionality

   * quick test on the fixed reports. verify the relate document is udpated.

refer:Kondor+ Adaptor Bug Tracking

3. verify the binary package can work .
   * verify whether the package structure is ok.
   * verify whether the jar file includes more un-usfull file
   * verify whether the configuration file is in correct format.
   * verify the obfucation output and the binarys are uploaded to share driver

   * etc.

refer  K+ Adaptor Validation before Release -> Common Checking

  This is the last change to filter out error, be careful.

4 put the binary and source file to share drive

5. update the report to be fixed in this release

escalate to : dev queue manager - rtns internal

status: wating deployment

note:

K+ Adapter v2.X.X is released.

The bug fix of this report is included in it.

6. write release note including

* new functionality

* fixed reports


7. review this release note with your coordinator, your manager, the more the better.

   think more before send it out.
  This is our commitment.

8.  upload the adapter binary, install guide to bizbuzz
    binary: https://transactions.thomsonreuters.com/asp/intranet/Filebase/EditComponent.aspx?uid=1544
    release note should be paste here.

    guide:https://transactions.thomsonreuters.com/asp/intranet/filebase/editcomponent.aspx?uid=7786

9. add the adaptor to RTNS RXXXX release page

Example:RTNS 2.8.0.0 Release 3

https://transactions.thomsonreuters.com/asp/intranet/releases/releaseShow.aspx?releaseID=27906

10. send out email about this release.


11. create tag for this relsase.
  such as T2.8.1_2.4.0             T$TRTNReleaseVersion_K+AdapterVersion

12. <conditional> create branch for this release  if this release will be available to customer