Skip to content

Commit

Permalink
job:#6556 Updated the HOWTO document and removed this:
Browse files Browse the repository at this point in the history
  - Go to the bp.doc plug-in and search under that plug-in for the old
version 
   number(example: 1.5.1)
  RESULT - Several html files are found

  - Copy the new version (ex 1.5.2)  to the Windows Clipboard

  - Work through the Search view in Eclipse and for each match found
open the 
   file in MS Word and update the version using MS Word.
   
       IMPORTANT: 
         1) Do not update any HTML file versions inside eclipse.
Navigate
            to the file on disk and edit the file with MS Word.
         2) The Release Notes and What's New files should be written
with 
            MS Word "Save As..." as type "Web Page, Filtered"
                  

                
We are not maintaining MS html "filtered" format anymore.  I did so
based on this chat:
[5/11/15, 1:27:01 PM] Keith Brown: I just got a text message for your "I
can do it"
[5/11/15, 2:58:40 PM] Bob Mulvey: I bumped the version in a fork
[5/11/15, 2:59:05 PM] Bob Mulvey: I did not do anything with the html
files that we use to have to update with MS Word
[5/11/15, 2:59:09 PM] Bob Mulvey: Is that OK?
[5/11/15, 2:59:30 PM] Bob Mulvey: Should those instructions be pulled
form the HOWTO now?
[5/11/15, 3:00:39 PM] Keith Brown: hmm.  My general feeling is that is
OK.
[5/11/15, 3:00:51 PM] Keith Brown: The release notes and what's new
we'll touch before a release for sure
[5/11/15, 3:01:30 PM] Keith Brown: I think the only other is the oss.htm
that just uses the version in a path.  We could probably generalize that
reference since we don't have the Mentor Legal Eagles looking over us.
[5/11/15, 3:01:46 PM] Bob Mulvey: OK
  • Loading branch information
rmulvey committed May 11, 2015
1 parent ffa83d6 commit 5273ba6
Show file tree
Hide file tree
Showing 197 changed files with 22,924 additions and 22,939 deletions.
143 changes: 64 additions & 79 deletions doc-bridgepoint/process/HOWTO-update-the-BP-version-number.md
Original file line number Diff line number Diff line change
@@ -1,79 +1,64 @@
# HOWTO-update-the-BP-version-number.txt


BridgePoint Technical Note
HOWTO Update the BridgePoint Version Number


Abstract
--------
This note describes the steps to be performed in order to update or "bump"
the version number of BridgePoint.

History
-------
None.

Document References
-------------------
None

Background
----------
It is the policy of the BridgePoint development team to update the version
number of BridgePoint with each external delivery of the code. This mostly
involves updating the plug-in version numbers.

Intended Audience
-----------------
This document is intended for the BridgePoint developers.

Steps
-----

- Turn off Build Automatically if it is turned on

- Update your development workspace with the latest version from github master
of all plug-in and support projects (e.g. installer, utilities)

- Create an issue in github for the version bump.

- Branch the xtuml/bridgepoint repository.

- Edit bp.internal.tools/update_BP_version.xml to contain the new version and
commit this to the issue used for the version bump.
- Right-click update_BP_version.xml, select "Run As > Ant Build"

- Go to the bp.doc plug-in and search under that plug-in for the old version
number(example: 1.5.1)
RESULT - Several html files are found

- Copy the new version (ex 1.5.2) to the Windows Clipboard

- Work through the Search view in Eclipse and for each match found open the
file in MS Word and update the version using MS Word.

IMPORTANT:
1) Do not update any HTML file versions inside eclipse. Navigate
to the file on disk and edit the file with MS Word.
2) The Release Notes and What's New files should be written with
MS Word "Save As..." as type "Web Page, Filtered"
- Select all projects in the workspace, refresh them to pick up the changes

R Version update is now complete, all files that must be modified are now
"dirty" in your workspace.

- Use "Team > Synchronize Workspace" to compare the locally changed projects
with the root of the branch. Use the code change scraper to get the list of
changed files.

- Commit and push the files changed with this work. Record the changed files
list in the commit message. As always, commit against the issue for this
task.

- Create a pull request for the branch.

- Merge the pull request.


# HOWTO-update-the-BP-version-number.txt


BridgePoint Technical Note
HOWTO Update the BridgePoint Version Number


Abstract
--------
This note describes the steps to be performed in order to update or "bump"
the version number of BridgePoint.

History
-------
None.

Document References
-------------------
None

Background
----------
It is the policy of the BridgePoint development team to update the version
number of BridgePoint with each external delivery of the code. This mostly
involves updating the plug-in version numbers.

Intended Audience
-----------------
This document is intended for the BridgePoint developers.

Steps
-----

- Turn off Build Automatically if it is turned on

- Update your development workspace with the latest version from github master
of all plug-in and support projects (e.g. installer, utilities)

- Create an issue in github for the version bump.

- Branch the xtuml/bridgepoint repository.

- Edit bp.internal.tools/update_BP_version.xml to contain the new version and
commit this to the issue used for the version bump.
- Right-click update_BP_version.xml, select "Run As > Ant Build"

- Select all projects in the workspace, refresh them to pick up the changes

R Version update is now complete, all files that must be modified are now
"dirty" in your workspace.

- Use "Team > Synchronize Workspace" to compare the locally changed projects
with the root of the branch. Use the code change scraper to get the list of
changed files.

- Commit and push the files changed with this work. Record the changed files
list in the commit message. As always, commit against the issue for this
task.

- Create a pull request for the branch.

- Merge the pull request.


2 changes: 1 addition & 1 deletion src/installer/build_installer_bp.sh
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ if [ $# -lt 5 ]; then
echo " staging_path -- path to the location of the Eclipse bases and BridgePoint deliverables"
echo " output_dir -- path to the location to output the installers"
echo " os - windows, linux or osx"
echo " release_version -- e.g. 5.0.0"
echo " release_version -- e.g. 5.1.0"
echo " optional:"
echo " SCP_UPLOAD_FOLDER_SPEC -- folder specification for scp upload: [email protected]:/myfolder"
echo
Expand Down
2 changes: 1 addition & 1 deletion src/installer/install_linux.xml
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
-->
<info>
<appname>BridgePoint for Linux (by OneFact.net)</appname>
<appversion>5.0.0</appversion>
<appversion>5.1.0</appversion>
</info>

<!--
Expand Down
2 changes: 1 addition & 1 deletion src/installer/install_windows.xml
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
-->
<info>
<appname>BridgePoint for Windows (by OneFact.net)</appname>
<appversion>5.0.0</appversion>
<appversion>5.1.0</appversion>
</info>

<!--
Expand Down
2 changes: 1 addition & 1 deletion src/installer/post_install_script.sh
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
#

echo Starting post-install script
BPVER=5.0.0
BPVER=5.1.0

#===============================================================================
# UTILITY FUNCTIONS
Expand Down
58 changes: 29 additions & 29 deletions src/org.xtuml.bp.als.oal/plugin.xml
Original file line number Diff line number Diff line change
@@ -1,29 +1,29 @@
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin
id="org.xtuml.bp.als.oal"
name="BridgePoint Oal Plug-in"
version="5.0.0"
provider-name="xtUML.org"
class="org.xtuml.bp.als.oal.OalPlugin">

<runtime>
<library name="oal.jar">
<export name="*"/>
</library>
</runtime>
<requires>
<import plugin="org.eclipse.core.runtime"/>
<import plugin="org.eclipse.ui"/>
<import plugin="org.eclipse.ui.ide"/>
<import plugin="org.eclipse.ui.views"/>
<import plugin="org.eclipse.jface.text"/>
<import plugin="org.eclipse.ui.workbench.texteditor"/>
<import plugin="org.eclipse.ui.editors"/>
<import plugin="org.xtuml.bp.core"/>
<import plugin="org.eclipse.core.resources"/>
<import plugin="org.antlr"/>
</requires>


</plugin>
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin
id="org.xtuml.bp.als.oal"
name="BridgePoint Oal Plug-in"
version="5.1.0"
provider-name="xtUML.org"
class="org.xtuml.bp.als.oal.OalPlugin">

<runtime>
<library name="oal.jar">
<export name="*"/>
</library>
</runtime>
<requires>
<import plugin="org.eclipse.core.runtime"/>
<import plugin="org.eclipse.ui"/>
<import plugin="org.eclipse.ui.ide"/>
<import plugin="org.eclipse.ui.views"/>
<import plugin="org.eclipse.jface.text"/>
<import plugin="org.eclipse.ui.workbench.texteditor"/>
<import plugin="org.eclipse.ui.editors"/>
<import plugin="org.xtuml.bp.core"/>
<import plugin="org.eclipse.core.resources"/>
<import plugin="org.antlr"/>
</requires>


</plugin>
Loading

0 comments on commit 5273ba6

Please sign in to comment.