falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Srikanth Sundarrajan <srik...@hotmail.com>
Subject RE: Falcon site moved to git
Date Tue, 15 Mar 2016 10:12:52 GMT
Thanks Pallavi. With this can we look to keep the doc changes in trunk live on the site with
every patch ? Does it make sense to update the site sync steps while merging pull requests
? Or this step included in the commit tool ?

Regards
Srikanth Sundarrajan

> Date: Mon, 14 Mar 2016 14:00:22 +0530
> Subject: Falcon site moved to git
> From: pallavi.rao@inmobi.com
> To: dev@falcon.apache.org
> 
> http://falcon.apache.org/ is now being powered by content in git (asf-site
> branch). This removes the dependency Falcon had on svn.
> 
> As before, the fresh docs will need to be pushed during a release. I have
> checked in a pretty simplistic script to pull docs from the release branch.
> I have also updated
> https://cwiki.apache.org/confluence/display/FALCON/How+to+update+site with
> instructions on how to publish to the site.
> 
> Balu,
> You will be the guinea pig to test out the new process during the 0.10
> release :-). Let me know if you run into any issues.
> 
> Thanks,
> Pallavi
> 
> -- 
> _____________________________________________________________
> The information contained in this communication is intended solely for the 
> use of the individual or entity to whom it is addressed and others 
> authorized to receive it. It may contain confidential or legally privileged 
> information. If you are not the intended recipient you are hereby notified 
> that any disclosure, copying, distribution or taking any action in reliance 
> on the contents of this information is strictly prohibited and may be 
> unlawful. If you have received this communication in error, please notify 
> us immediately by responding to this email and then delete it from your 
> system. The firm is neither liable for the proper and complete transmission 
> of the information contained in this communication nor for any delay in its 
> receipt.
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message