We can push it before then, too.  All my script does is:

/usr/local/bin/svn export --force 
http://svn.apache.org/repos/asf/lucene/mahout/site/publish 
/www/lucene.apache.org/mahout/

This is generally what I do when we do a release.  Note, you have to wait 24 
hours after pushing the button to announce, as it can take time to propogate.

-Grant

On Mar 15, 2010, at 11:27 AM, Robin Anil wrote:

> hit the send button soon...
> 
> the site src edit doesnt mean it will go live. It will go live only if the
> site is generated, and Grants script pushes it. I am confused about the time
> zone but its supposed to autorun everynight at some (not mentioned) time
> http://cwiki.apache.org/MAHOUT/howtoupdatethewebsite.html
> 
> Feel free to edit the release notes in the meantime.
> 
> Robin
> 
> On Mon, Mar 15, 2010 at 8:54 PM, Robin Anil <robin.a...@gmail.com> wrote:
> 
>> Yeah the site src edit doesnt mean it will go live. It will go live only if
>> the site is generated.
>> 
>> 
>> 
>> On Mon, Mar 15, 2010 at 8:50 PM, Benson Margulies 
>> <bimargul...@gmail.com>wrote:
>> 
>>> I hate to go back onto topic, but we appear to have the requisite 3
>>> votes and 72 hours. I plan to push the nexus button tonight, and then
>>> Robin or whoever can push the site material live.
>>> 
>>> On Mon, Mar 15, 2010 at 11:17 AM, Robin Anil <robin.a...@gmail.com>
>>> wrote:
>>>> ?
>>>> 
>>>>           <li>New: math and collections modules based on the high
>>>> performance Colt library </li>
>>>>           <li>Faster Frequent Pattern Growth(FPGrowth) using FP-bonsai
>>>> pruning</li>
>>>>           <li>Parallel Dirichlet process clustering (model-based
>>>> clustering algorithm)</li>
>>>>           <li>Parallel co-occurrence based recommender</li>
>>>>           <li>Parallel text document to vector conversion using LLR
>>> based
>>>> ngram generation</li>
>>>>           <li>Parallel Lanczos SVD(Singular Value Decomposition)
>>>> solver</li>
>>>>           <li>Shell scripts for easier running of algorithms, utilities
>>>> and examples</li>
>>>>           <li>... and much much more: code cleanup, many bug fixes and
>>>> performance improvements</li>
>>>> 
>>> 
>> 
>> 


Reply via email to