Christian Grobmeier wrote on Wed, Mar 13, 2013 at 07:41:32 +0100:
> It would be better if the person who pushed a change (most often the
> status page) would also publish the website right after. Otherwise the
> next publisher will never knew if publication is desired or not.
(speaking on my exper
Nice. Thanks!
On Wed, Mar 13, 2013 at 5:33 PM, Christian Grobmeier
wrote:
> On Wed, Mar 13, 2013 at 7:53 AM, Edward J. Yoon wrote:
>>> status page) would also publish the website right after. Otherwise the
>>
>> Thanks I see. To publish the website, do I only need to commit to
>> production like
On Wed, Mar 13, 2013 at 7:53 AM, Edward J. Yoon wrote:
>> status page) would also publish the website right after. Otherwise the
>
> Thanks I see. To publish the website, do I only need to commit to
> production like below?
Even easier. Its document here:
http://incubator.apache.org/guides/websit
> status page) would also publish the website right after. Otherwise the
Thanks I see. To publish the website, do I only need to commit to
production like below?
Log:
mrql added, changes to ripple.
Added:
websites/production/incubator/content/
- copied from r854238, websites/stagi
Hi folks,
from time to time I publish the website. Usually I check the diff
first, and it happens that I see changes which I didn't include. I am
then required to make a quick cross check and see if they are ok.
It would be better if the person who pushed a change (most often the
status page) wou
