<commit_before># HOWTO Create a New Build of xtUML Editor
### xtUML Project Technical Note

1. Abstract
-----------
This note describes the steps for creating a new build of xtUML Editor and 
publishing it on the interweb.

2. Document References
----------------------
[1] HOWTO update the BridgePoint version, https://github.com/xtuml/internal/blob/master/doc-internal/process/HOWTO-update-the-BP-version-number.txt  
[2] HOWTO upload the xtUML Editor, https://github.com/xtuml/internal/blob/master/doc-internal/process/HOWTO-upload-xtUML-editor-installer.md   

3. Steps
-------------
1.  Decide what the new version number for xtUML Editor will be  
2.  Create a tracking issue in CQ and git for the new xtUML Editor 
3. Assure that promotion process has been followed so that all changes
are present in the xtuml/internal repoistory's xtuml_editor_builder branch
4.  Update the Release Notes and What's New documents.  These are found under
com.mentor.nucleus.bp.doc.
5. Create a branch from these two branches from the xtuml/internal repository:

   xtuml_editor_builder
   xtuml_editor
   
to names that append the version number to them.  These are the branches you
should work in while creating this release.  
6.  Bump the version in the xtuml_editor_builder branch [1] to the desired version
for the new xtUML Editor.
7. Build the `xtuml_editor_builder_<version>` branch on the build server.  This shall be the 
binary release of the xtUML Editor.  
8.  When the build is complete, test this release candidate on both Windows and 
Linux but while waiting for the build, the remaining steps can be taken to 
complete the xtUML Editor source release.
9. Merge xtuml/internal `branch xtuml_editor_builder_<version>` into  
xtuml/internal `xtuml_editor_<version>`.  This is merging the binary release branch
changes into what will be the source code release.
10. Move the `internal/xtuml_editor_<version>` branch into the editor repository    
	* branch the editor repository
	* delete all src/* projects that will be updated. All projects are deleted
	except for the following:  
		* doc-editor
		* org.xtuml.sql.upgrade
		* org.xtuml.sql.upgrade.bin  
11. Commit the deletion of files  
12. Copy the new src/* from your local machines location for the  
`internal/xtuml_editor_<version>` branch into the editor branch created in step 10.
	* commit the new source
13. Build and test the xtuml/editor branch
14. Once the binary and source release are both tested, promote the 
xtuml/editor branch into editor/origin/master


15. Upload the installers to Amazon S3 [2]  
16. Update the xtUML.org website with the new Release Notes  
17. Notify Jayne she can do a mailing indicating a new release of xtUML Editor is available  
18. Post to the xtuml.org forum indicating the new release is available  
19. Bump the BP development version past the xtUML Editor version  
20. Done
<commit_msg>Update HOWTO-create-xtUML-Editor.md<commit_after># HOWTO Create a New Build of xtUML Editor
### xtUML Project Technical Note

1. Abstract
-----------
This note describes the steps for creating a new build of xtUML Editor and 
publishing it on the interweb.

2. Document References
----------------------
[1] HOWTO update the BridgePoint version, https://github.com/xtuml/internal/blob/master/doc-internal/process/HOWTO-update-the-BP-version-number.txt  
[2] HOWTO upload the xtUML Editor, https://github.com/xtuml/internal/blob/master/doc-internal/process/HOWTO-upload-xtUML-editor-installer.md   

3. Steps
-------------
1.  Decide what the new version number for xtUML Editor will be  
2.  Create a tracking issue in CQ and git for the new xtUML Editor 
3. Assure that promotion process has been followed so that all changes
are present in the xtuml/internal repoistory's xtuml_editor_builder branch
4.  Update the Release Notes and What's New documents.  These are found under
com.mentor.nucleus.bp.doc.
5. Create a branch from these two branches from the xtuml/internal repository:
  * xtuml_editor_builder
  * xtuml_editor  
Use names that append the version number to the existing branch names.  These are the branches you
should work in while creating this release.  
6.  Bump the version in the xtuml_editor_builder branch [1] to the desired version
for the new xtUML Editor.
7. Build the `xtuml_editor_builder_<version>` branch on the build server.  This shall be the 
binary release of the xtUML Editor.  
8.  When the build is complete, test this release candidate on both Windows and 
Linux but while waiting for the build, the remaining steps can be taken to 
complete the xtUML Editor source release.  
9. Merge xtuml/internal `branch xtuml_editor_builder_<version>` into  
xtuml/internal `xtuml_editor_<version>`.  This is merging the binary release branch
changes into what will be the source code release.  
10. Move the `internal/xtuml_editor_<version>` branch into the editor repository    
* branch the editor repository
* delete all `src/*` projects that will be updated. All projects are deleted
except for the following:
  * doc-editor
  * org.xtuml.sql.upgrade
  * org.xtuml.sql.upgrade.bin  
11. Commit the deletion of files  
12. Copy the new src/* from your local machines location for the `internal/xtuml_editor_<version>` branch into the editor branch created in step 10.  
* commit the new source  
13. Build and test the xtuml/editor branch  
14. Once the binary and source release are both tested, promote the xtuml/editor branch into editor/origin/master  

15. Upload the installers to Amazon S3 [2]  
16. Update the xtUML.org website with the new Release Notes  
17. Notify Jayne she can do a mailing indicating a new release of xtUML Editor is available  
18. Post to the xtuml.org forum indicating the new release is available  
19. Bump the BP development version past the xtUML Editor version  
20. Done  

{'fraction_non_alphanumeric': 0.06813901729155966, 'fraction_numerical': 0.0140386920047937, 'mean_word_length': 3.6961414790996785, 'pattern_counts': {'":': 0, '<': 13, '<?xml version=': 0, '>': 13, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, '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': '5898', 'n_tokens_mistral': 1764, 'n_tokens_neox': 1687, 'n_words': 784}