Release Process - Revision history

MatMarcus: /* Semi-automated from here */

2010-11-10T17:05:41Z

‎Semi-automated from here

MatMarcus: /* Semi-automated from here */

2010-11-10T16:47:00Z

‎Semi-automated from here

FosterBrereton at 21:04, 4 November 2010

2010-11-04T21:04:11Z

MatMarcus: /* Semi-automated from here */

2010-10-29T17:10:42Z

‎Semi-automated from here

SeanParent: /* Semi-automated from here */

2009-02-15T00:50:41Z

‎Semi-automated from here

MatMarcus: /* Semi-automated from here */

2008-12-23T19:06:18Z

‎Semi-automated from here

MatMarcus: /* Semi-automated from here */

2008-11-13T18:48:36Z

‎Semi-automated from here

MatMarcus: /* stlabconnect */

2008-11-07T15:58:49Z

‎stlabconnect

MatMarcus: /* Semi-automated from here */

2008-11-07T02:34:24Z

‎Semi-automated from here

MatMarcus: /* Build and test all mac targets */

2008-11-06T21:57:49Z

‎Build and test all mac targets

@@ Line 166: / Line 166: @@
 p4 submit
 </pre>
-* Upload to SourceForge 10 files (sftp: frs.sourceforge.net using sftp with your sourceforge credentials. remote path: /uploads. No two files in your entire release library can have the same name). Create the source tarball/zip using the perl script
+* Upload to SourceForge 10 files (sftp: frs.sourceforge.net using sftp with your sourceforge credentials. See https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download . No two files in your entire release library can have the same name). Create the source tarball/zip using the perl script
 <code>
   perl $ADOBE_ROOT/adobe_platform_libraries/tools/package_distros.pl

@@ Line 184: / Line 184: @@
 *** Name: <code>apl_1.0.XX.tgz</code>
 *** Name: <code>apl_1.0.XX.zip</code>
-* Go to http://sourceforge.net/project/admin/editpackages.php?group_id=132417
+* Go to https://sourceforge.net/project/admin/explorer.php?group_id=132417
 ** Click <code>[Add Release]</code> next to <code>adobe-source</code>
 ** Follow basic form to add details to the release (release name: (e.g.) 1.0.31)

@@ Line 229: / Line 229: @@
    ./bin/stlab.sh  #remotely expands the tarball and moves the new docs into place.
 </pre>
 ===Scripts===
 ====opensource_rsync.sh====

@@ Line 116: / Line 116: @@
 == Semi-automated from here ==
 * rev <code>$ADOBE_ROOT/adobe_source_libraries/read_me.html</code> with current version numbers for "automated build" instructions.
-* Update <code>$ADOBE_ROOT/adobe_source_libraries/tools/patch_boost.sh</code> if a new version of boost has been released. Also update boost version numbers in $ADOBE_ROOT/adobe_source_libraries/documentation/html/asl_readme.html and <code>$ADOBE_ROOT/adobe_platform_libraries/tools/verify.sh</code>. Furthermore, make sure that the boost patch file name is updated, e.g. <code>$ADOBE_ROOT/adobe_source_libraries/tools/boost_1_37_0_patches.txt</code>.
+* Update <code>$ADOBE_ROOT/adobe_source_libraries/tools/patch_boost.sh</code> if a new version of boost has been released. Also update boost version numbers in $ADOBE_ROOT/adobe_source_libraries/documentation/html/asl_readme.html and <code>$ADOBE_ROOT/adobe_platform_libraries/tools/verify.sh</code>. Furthermore, make sure that the boost patch file name is updated, e.g. <code>$ADOBE_ROOT/adobe_source_libraries/tools/boost_1_44_0_patches.txt</code>.
-* Update the boost patch file contents e.g. <code>$ADOBE_ROOT/adobe_source_libraries/tools/boost_1_37_0_patches.txt</code> . For example, under win32, generation of the patch file might look like:
+* Update the boost patch file contents e.g. <code>$ADOBE_ROOT/adobe_source_libraries/tools/boost_1_44_0_patches.txt</code> . For example, under win32, generation of the patch file might look like:
 <pre>
-## given a clean copy of boost in $ADOBE_ROOT/diffable_boost_1_37_0
+## given a clean copy of boost in $ADOBE_ROOT/diffable_boost_1_44_0
 cd  $ADOBE_ROOT/adobe_source_libraries
-diff -wur --unidirectional-new-file -x status -x adobe_information -xp4config -x bin.v2 ../diffable_boost_1_37_0 ../boost_libraries > ./tools/boost_1_37_0_patches.txt
+diff -wur --unidirectional-new-file -x status -x adobe_information -xp4config -x bin.ntx86 -x bin.cygwinx86 -x bin.v2 ../diffable_boost_1_44_0 ../boost_libraries > ./tools/boost_1_44_0_patches.txt
 </pre>
 Note, however, that the diffs for boost filesystem's wrong_line_end test may be spurious (depending on perforce line ending settings). As of 9/2008 that file has *not* been patched. Also be sure not to pick up p4config files or to add them to p4. Note: if boost patches was updated externally by the opensource community then those patches should be applied to the internal boost first.

@@ Line 159: / Line 159: @@
 </pre>
-* Integrate from opensource //adobe_source_libraries to //source_release, and same for platform:
+* Integrate from //adobe_source_libraries to //source_release, and same for platform:
 <pre>
@@ Line 192: / Line 192: @@
 *** Go to "Notice" section at the bottom, hit "I'm sure", and post it.
 * Update the utility scripts (p4checkout) if need be
-* Update opensource.adobe.com with new documentation: once you have rsynced up the files, by running opensource_rsync.sh, you go to http://webpush.macromedia.com/stlab.adobe.com/ , provide LDAP info, Push the "Check all push boxes" button, then go through the list and uncheck the push boxes for the directories (amg/, gil/ and performance/). When that's ready, hit the "Push and/or Delete!" button at either the top or bottom of the page
+* Update stlab.adobe.com with new documentation: once you have rsynced up the files, by running opensource_rsync.sh, you go to http://webpush.macromedia.com/stlab.adobe.com/ , provide LDAP info, Push the "Check all push boxes" button, then go through the list and uncheck the push boxes for the directories (amg/, gil/ and performance/). When that's ready, hit the "Push and/or Delete!" button at either the top or bottom of the page
 * Test the net setup scrips on both platforms. It's good to choose paths with spaces in them for robustness. Note: sometimes it takes SF a bit of time ot propagate the uploaded files to the mirrors/download areea.
 * Update internal website with new documentation (not necessary most releases, unless changed):

@@ Line 289: / Line 289: @@
 </pre>
    Check that it worked by examining the label in P4V, comparing it to the previous label
 * Update the [[Annotated List of Boost Patches]]
 * Mail an announcement to asl-users@adobe.com

@@ Line 166: / Line 166: @@
 p4 submit
 </pre>
-* Upload to SourceForge 8 files (sftp: frs.sourceforge.net using sftp with your sourceforge credentials. remote path: /uploads. No two files in your entire release library can have the same name). Create the source tarball/zip using the perl script
+* Upload to SourceForge 10 files (sftp: frs.sourceforge.net using sftp with your sourceforge credentials. remote path: /uploads. No two files in your entire release library can have the same name). Create the source tarball/zip using the perl script
 <code>
   perl $ADOBE_ROOT/adobe_platform_libraries/tools/package_distros.pl
@@ Line 173: / Line 173: @@
 *** <code>asl_1.0.XX_begin_mac.tgz</code> (includes app, dependencies, and examples folder--see the <code>package_distros.pl</code> script for details.)
 *** <code>asl_1.0.XX_begin_win.zip</code> (includes app, dependencies, runtime libs, and examples folder--see the <code>package_distros.pl</code> script for details.)
 ** Net setup scripts
 *** <code>asl_1.0.XX_net_setup.sh</code>

@@ Line 17: / Line 17: @@
 # win users can ssh into their mac machine
 # this step assumes that bjam is installed
-export ADOBE_ROOT=`p4 where //adobe_platform_libraries/... | perl -MFile::Basename -ane 'print dirname dirname $F[2]'`
+export ADOBE_ROOT=`p4 where //adobe_platform_libraries/... | perl -MFile::Basename -ane 'print dirname dirname $F[2]'` && \
-cd $ADOBE_ROOT/adobe_platform_libraries
+cd $ADOBE_ROOT/adobe_platform_libraries && \
-bjam -j3 debug release
+bjam -j3 debug release && \
-cd $ADOBE_ROOT/adobe_platform_libraries/xcode_ide/begin.xcodeproj
+cd $ADOBE_ROOT/adobe_platform_libraries/xcode_ide/begin.xcodeproj && \
-xcodebuild -configuration Debug  ##case sensitive! (untested)
+xcodebuild -configuration Debug   && \
-xcodebuild -configuration Release  ##case sensitive! (untested)
+xcodebuild -configuration Release  && \
-#also build 64bit ASL debug/release
+#also build 64bit ASL debug/release && \
-cd $ADOBE_ROOT/adobe_source_libraries
+cd $ADOBE_ROOT/adobe_source_libraries && \
-bjam -j3 debug address-model=64
+bjam -j3 debug address-model=64 && \
 bjam -j3 release address-model=64 architecture=combined
 #end