This is an automated email from the ASF dual-hosted git repository.
aharui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-asjs.wiki.git
The following commit(s) were added to refs/heads/master by this push:
new 07b7ab3 add steps I use to check versions.
07b7ab3 is described below
commit 07b7ab376250b64e6c4f5cca4c2cacebabf95448
Author: aharui <[email protected]>
AuthorDate: Mon Oct 1 11:48:09 2018 -0700
add steps I use to check versions.
---
Release-Manager-Notes.md | 91 ++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 91 insertions(+)
diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
index 2eb7dde..5be4cd5 100644
--- a/Release-Manager-Notes.md
+++ b/Release-Manager-Notes.md
@@ -39,6 +39,97 @@ Next, go find the staging repository for Royale in the
[Apache Nexus](https://re
Some times, during the creation of an RC, you'll see something you want to
change before you tell everyone to start examining the RC. In order to use the
"maven" step again, you will have to undo things as described in "Canceling an
RC", but also remove any tags in Git that the "maven" step created. Make sure
the repos are synced up and then on each of the 3 repos do "git tag" to list
the tags. Look for the tag for that RC. It will look like
"org.apache.royale.compiler-0.9.0-rc2" (o [...]
+## Checking Versions (Before you start)
+
+Theoretically, you will never need to do this, but sometimes the version
numbers used in the builds will get out of sync in the repos due to incorrect
reverts or other changes going on in the develop branch. Here are the tests I
use to check that the version numbers are correct. You will need to use grep,
so on Windows, you'll probably need Cygwin or some other BASH shell.
+
+The following uses the example of trying to release 0.9.4. Where an example
also uses 0.9.3 or 0.9.5 it is essentially testing that version numbers aren't
ahead or behind. In each repo, run:
+
+`git pull --rebase`
+
+This syncs up the repo.
+
+`git branch --all`
+
+This displays all of the branches. There should be branches of the form
'remotes/origin/release/0.9.0' for previous releases, but not for the current
release. If there is, delete the branch for this version (assuming it doesn't
have any important changes).
+
+`git tag`
+
+This displays all of the tags. There should be tags of the form
'apache-royale-0.9.0' for previous releases, but not for the current release.
If there is, delete the tag (maybe ask on dev@ if there is any reason why that
tag exists, or check commits@ for when it got created.
+
+**royale-compiler**
+
+Run 'ant wipe-all' to remove all generated code. Then run:
+
+`grep -r '0\.9\.4' *`
+
+This should result in lots of files having '0.9.4-SNAPSHOT' and
build.properties having just '0.9.4'. If entries were added to RELEASE_NOTES
then 0.9.4 should be in RELEASE_NOTES as well.
+
+`grep -r '0\.9\.3' *`
+
+This should only show RELEASE_NOTES, if anything
+
+`grep -r '0\.9\.5' *`
+
+This should not return anything.
+
+**royale-typedefs**
+
+Run "ant wipe" to remove all generated code. Then run:
+
+`grep -r '0\.9\.4' *`
+
+This should result in lots of files having '0.9.4-SNAPSHOT' (and not just
"0.9.4"). The top-level pom.xml should have:
+
+'<royale.compiler.version>0.9.4-SNAPSHOT</royale.compiler.version>'
+
+There shouldn't be any other files with that version in it.
+
+`grep -r '0\.9\.3' *`
+
+No files should mention the older version
+
+`grep -r '0\.9\.5' *`
+
+No files should mention the newer version.
+
+**royale-asjs**
+
+Run "ant super-clean" to remove all generated code. Then run:
+
+'grep -r '0\.9\.4' * | grep -v @productversion'
+
+The grep -v filters out any hits from ASDoc @productversion so it is easier to
see the build-related versions. This should result in lots of files having
'0.9.4-SNAPSHOT' (and not just "0.9.4"). The top-level pom.xml should have:
+
+'<royale.compiler.version>0.9.4-SNAPSHOT</royale.compiler.version>'
+
+and
+
+'<royale.typedefs.version>0.9.4-SNAPSHOT</royale.typedefs.version>'
+
+The following files will have just plain "0.9.4" in it:
+
+* build.properties
+* various -app.xml files in examples
+* flex-sdk-description.xml
+* npm/js-only/package.json
+* npm/js-swf/package.json
+* package.json
+* a few .as files in ASDoc comments.
+* the RELEASE_NOTES
+
+`grep -r '0\.9\.3' * | grep -v @productversion`
+
+This should not only return the RELEASE_NOTES and a few files with ASDOC, but
also the main pom.xml where it says:
+
+`<tag>release/0.9.3</tag>`
+
+The tag should be for the older version as the Maven release process will
update the version with the tag it makes for the release branch. Not sure what
will happen if that is out of sync.
+
+`grep -r '0\.9\.5' *`
+
+No files should mention the newer version.
+
## Other setup
Make sure you have a settings.xml in your .m2 folder that has credentials for
deploying artifacts to repository.apache.org. Follow instructions here:
https://maven.apache.org/settings.html. Make sure you have entries like:
