Hi Kit, 
     
    I've fixed our deployBabelLive.sh script to enable deploying a
    tagged release.  It operates in exactly the same way as it did with
    CVS. 
     
    Behind the scenes, since Git operates with complete clones, we
    simply use the staging area's Git clone  
     
    dd /path/to/staging 
    git checkout $RTAG  <-- use the staging area to checkout the tag into the working directory 
    rsync -a --delete --exclude "addons/" --exclude ".git" /path/to/staging/ /path/to/live/  <-- use RSYNC to sync the staging code (currently on the tag) 
    git checkout master  <-- return staging back to the "HEAD" stream 
     
    I've pushed R_0_201303022000 and it all seems to work; but please
    confirm. 
     
    Thanks, 
     
    Denis 
     
     
    On 06/14/2013 11:45 AM, Kit Lo wrote: 
     
    
      Thanks, Denis! 
         
        If the Git release process is
          still the same (no change after your recent Git check-in
          process fix), then I think the tag is ready. Please try to
          release "R_0_201303022000" to the live server. I did not check
          in any other changes after that. 
         
        Thanks, 
          Kit Lo 
          Eclipse Babel Project Lead 
          IBM Eclipse SDK (IES) Globalization Technical Lead 
          IBM Rational solution for Collaborative Lifecycle Management
          (CLM) Globalization Technical Lead 
         
         Denis Roy ---06/14/2013 11:27:37
          AM---Hi Kit, Looks like I authored some docs for the Git
          release process some time ago: 
         
        From: Denis Roy
          <denis.roy@xxxxxxxxxxx> 
        To: babel-dev@xxxxxxxxxxx,  
        Date: 06/14/2013 11:27 AM 
        Subject: Re: [babel-dev] Prepare for Kepler 
        Sent by: babel-dev-bounces@xxxxxxxxxxx 
       
      
  
       
       
      Hi Kit, 
         
        Looks like I authored some docs for the Git release process some
        time ago: 
       
        http://wiki.eclipse.org/Babel_/_Server_Tool_Development_Process#Release_process 
         
         
        In short: 
        -  create a new tag in Git, like you used to in CVS. 
        - since tagging is a local process, it must be pushed to the
        remote.  See docs, this is not a simple push. 
        - once it's pushed, we run the release process on the server. 
         
        I haven't updated our release process on the server.  Once you
        have your release tagged and ready, I will do just that, then
        we'll be set for future releases. 
         
        Denis 
         
         
         
       
      On 06/11/2013 05:01 PM, Kit Lo wrote:
      
         
        Thanks, Denis! 
         
          I tested out the new enhancement to extract source files from
          Git repositories. The code worked beautifully! I had another
          enhancement to support Dojo _javascript_ files. That also worked
          without a hitch! 
         
          I'm happy to announce that Babel now officially supports
          translation of Dojo _javascript_ (.js) files. Eclipse Orion
          project is our first client! 
         
          Anyone is welcome to test out the eclipse 4.3 and
          eclipse.orion 3.0 projects at the Babel Staging server. 
         
          Denis, I feel that we are ready to push these 2 new
          enhancements to the live server, although I may still have to
          touch up a few scripts to publish the Orion language packs to
          the Eclipse download server. Please help figure out (and
          document) the new release process. I will try that out when
          it's ready. 
         
          Thanks a lot for your help! 
         
          Regards, 
          Kit Lo 
          Eclipse Babel Project Lead 
          IBM Eclipse SDK (IES) Globalization Technical Lead 
          IBM Rational solution for Collaborative Lifecycle Management
          (CLM) Globalization Technical Lead 
           
         Denis Roy ---06/11/2013 10:40:41
          AM---Hi Kit, Sorry for the delay on this.  I've fixed the Git
          check-in process that 
         
          From: Denis Roy <denis.roy@xxxxxxxxxxx> 
          To: babel-dev@xxxxxxxxxxx,  
          Date: 06/11/2013
          10:40 AM 
          Subject: Re:
          [babel-dev] Prepare for Kepler 
          Sent by: babel-dev-bounces@xxxxxxxxxxx
        
  
           
           
          Hi Kit, 
           
          Sorry for the delay on this.  I've fixed the Git check-in
          process that will grab Git HEAD and publish to staging.  I've
          also noticed that it has picked up a bunch of files that you
          had pushed recently, such as: 
          classes/export/source_files_for_orion/babelEditorPlugin.html 
          classes/export/source_files_for_orion/babelGitPlugin.html 
          classes/export/source_files_for_orion/babelUiPlugin.html 
          classes/export/source_files_for_orion/babelUsersPlugin.html 
          .. and so on. 
           
          FWIW, I was using "git fetch" instead of "git pull". 
           
          We'll need to figure out what the new process for a release
          will be.  Git supports the notion of tags, like CVS, so our
          process will likely not change.  When you're ready to push a
          release to the live version, please let me know and I'll work
          it out. 
           
          Denis 
           
           
           
          On 05/29/2013 12:06 PM, Kit Lo wrote: 
        
           
            Denis, 
             
            Kepler is approaching RC2. Please help fix the Babel Git
            check-in process so that we can start extracting files for
            projects in Kepler and start building the Kepler language
            packs. Thanks for your help! 
             
            Kit Lo 
            Eclipse Babel Project Lead 
            IBM Eclipse SDK (IES) Globalization Technical Lead 
            IBM Rational solution for Collaborative Lifecycle Management
            (CLM) Globalization Technical Lead  
           
             
         
       
      _______________________________________________ 
          babel-dev mailing list 
          babel-dev@xxxxxxxxxxx 
        https://dev.eclipse.org/mailman/listinfo/babel-dev 
        
      
         
       
      
       
      _______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev
 
     
     
    
  
 |