uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marshall Schor <...@schor.com>
Subject Re: Part of our website not being published via svn pubsub?
Date Mon, 11 Mar 2013 14:46:18 GMT
pinging - still have no resolution on this.

Note: earlier reply made wrong assumption that our site was CMS based; see next
note.

Should we post a Jira on this?

-Marshall


On 3/7/2013 4:14 PM, Marshall Schor wrote:
> On 3/7/2013 2:34 PM, Daniel Shahaf wrote:
>> Configure the CMS build system or extpaths.txt to build that path in the
>> staging site.
>> http://www.apache.org/dev/cmsref
> Our website is not CMS based;  it's built with Anakia and then commits to the
> docs/ directory triggers the svn pubsub hook.
>
> The link you posted appears to be for sites built with the CMS build system, but
> I don't think our site uses this at all. 
>
> Can you be a bit more specific on what we should do / configure / change ?  For
> instance, where would we look for the extpaths.txt file?
>
> Thanks. -Marshall
>> Marshall Schor wrote on Thu, Mar 07, 2013 at 13:49:20 -0500:
>>> We moved our /d/ part of our tree to svnpubsub on December 19, 2012 (see notes
>>> below).  However, we now notice that updates to our svn tree
>>>
>>>           https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/
>>>
>>> don't seem to be getting published.
>>>
>>> Is there something more we need to do?
>>>
>>> -Marshall
>>>
>>>
>>>
>>> On 12/10/2012 12:29 PM, Joe Schaefer wrote:
>>>> No portion of your tree can depend on rsync
>>>> going forward, in particular everything in
>>>> uima.apache.org/d/ needs to be migrated to
>>>> svnpubsub.
>>>>
>>>>     --------------------------------------------------------------------------------
>>>>     *From:* Marshall Schor <msa@schor.com>
>>>>     *To:* infrastructure@apache.org
>>>>     *Sent:* Monday, December 10, 2012 12:22 PM
>>>>     *Subject:* UIMA on Santa's Naughty List (end of year migration deadline)
>>>>
>>>>     Hi Infra,
>>>>
>>>>     UIMA moved to svnpubsub quite a while ago.  Can you say why it's on the
list?
>>>>     Is it because we have a part of our website that we publish via a custom
rsync
>>>>     infra set up for us a while back (for the generated JavaDocs and PDFs)?

>>>>     We did
>>>>     that to avoid cluttering up SVN with large amounts of
>>>>     generated-from-source data.
>>>>
>>>>     If this is the reason, what action is needed on our part at this time
to
>>>>     get off
>>>>     of Santa's Naught List?
>>>>
>>>>     Thank you.
>>>>
>>>>     -Marshall Schor
>>>>
>>>>
>>>>     On 12/10/2012 10:17 AM, Joe Schaefer wrote:
>>>>     > It has come to my attention that some of the projects
>>>>     > that really need to see this message have failed to
>>>>     > pass it through moderation, so I've subbed myself to
>>>>     > all the relevant allow lists and resubmitted here.
>>>>     > If you've seen it already feel free to ignore this message.
>>>>     >
>>>>     >
>>>>     >
>>>>     > ----- Forwarded Message -----
>>>>     >> From: Joe Schaefer <joe_schaefer@yahoo.com <mailto:joe_schaefer@yahoo.com>>
>>>>     >> To: Apache Infrastructure <infrastructure@apache.org
>>>>     <mailto:infrastructure@apache.org>>
>>>>     >> Sent: Sunday, December 9, 2012 9:17 PM
>>>>     >> Subject: The bitter end of rsync-backed site management is coming
Jan 1.
>>>>     >>
>>>>     >>
>>>>     >> NOTE: If your project's site is using the CMS or svnpubsub
>>>>     >> right now you may disregard this note.
>>>>     >>
>>>>     >>
>>>>     >> If you project is listed below, you have yet to migrate your
>>>>     >> site to either the CMS or svnpubsub, which becomes mandatory
>>>>     >> starting January 1.  This note will serve as your FINAL reminder
>>>>     >> to start the process of filing a JIRA ticket with INFRA to
>>>>     >> request a migration to one of those two options prior to
>>>>     >> January 1, or face a hasty unannounced withdrawal of support
>>>>     >> for your website during the month of January upon processing
>>>>     >> of all remaining timely outstanding requests filed before Jan
1.
>>>>     >>
>>>>     >>
>>>>     >> Thanks for your diligence in this matter, further questions
>>>>     >> may be addressed to infrastructure@apache.org
>>>>     <mailto:infrastructure@apache.org>.
>>>>     >>
>>>>     >>
>>>>     >> SANTA'S NAUGHTY LIST:
>>>>     >> activemq.apache.org <http://activemq.apache.org/>
>>>>     >> apr.apache.org <http://apr.apache.org/>
>>>>     >> archive.apache.org <http://archive.apache.org/>
>>>>     >> buildr.apache.org <http://buildr.apache.org/>
>>>>     >> click.apache.org <http://click.apache.org/>
>>>>     >> commons.apache.org <http://commons.apache.org/>
>>>>     >> db.apache.org <http://db.apache.org/>
>>>>     >> directory.apache.org <http://directory.apache.org/>
>>>>     >> favicon.ico
>>>>     >> felix.apache.org <http://felix.apache.org/>
>>>>     >> forrest.apache.org <http://forrest.apache.org/>
>>>>     >> geronimo.apache.org <http://geronimo.apache.org/>
>>>>     >> hadoop.apache.org <http://hadoop.apache.org/>
>>>>     >> hbase.apache.org <http://hbase.apache.org/>
>>>>     >> hc.apache.org <http://hc.apache.org/>
>>>>     >> hive.apache.org <http://hive.apache.org/>
>>>>     >> jackrabbit.apache.org <http://jackrabbit.apache.org/>
>>>>     >> jmeter.apache.org <http://jmeter.apache.org/>
>>>>     >> juddi.apache.org <http://juddi.apache.org/>
>>>>     >> karaf.apache.org <http://karaf.apache.org/>
>>>>     >> lenya.apache.org <http://lenya.apache.org/>
>>>>     >> maven.apache.org <http://maven.apache.org/>
>>>>     >> ode.apache.org <http://ode.apache.org/>
>>>>     >> openjpa.apache.org <http://openjpa.apache.org/>
>>>>     >> openwebbeans.apache.org <http://openwebbeans.apache.org/>
>>>>     >> perl.apache.org <http://perl.apache.org/>
>>>>     >> pig.apache.org <http://pig.apache.org/>
>>>>     >> poi.apache.org <http://poi.apache.org/>
>>>>     >> portals.apache.org <http://portals.apache.org/>
>>>>     >> roller.apache.org <http://roller.apache.org/>
>>>>     >> santuario.apache.org <http://santuario.apache.org/>
>>>>     >> shiro.apache.org <http://shiro.apache.org/>
>>>>     >> sling.apache.org <http://sling.apache.org/>
>>>>     >> spamassassin.apache.org <http://spamassassin.apache.org/>
>>>>     >> struts.apache.org <http://struts.apache.org/>
>>>>     >> synapse.apache.org <http://synapse.apache.org/>
>>>>     >> tapestry.apache.org <http://tapestry.apache.org/>
>>>>     >> tcl.apache.org <http://tcl.apache.org/>
>>>>     >> tiles.apache.org <http://tiles.apache.org/>
>>>>     >> turbine.apache.org <http://turbine.apache.org/>
>>>>     >> tuscany.apache.org <http://tuscany.apache.org/>
>>>>     >> uima.apache.org <http://uima.apache.org/>
>>>>     >> velocity.apache.org <http://velocity.apache.org/>
>>>>     >> whirr.apache.org <http://whirr.apache.org/>
>>>>     >> wiki.apache.org <http://wiki.apache.org/>
>>>>     >> ws.apache.org <http://ws.apache.org/>
>>>>     >> xerce
>>>>     > s.apache.org
>>>>     >> xml.apache.org <http://xml.apache.org/>
>>>>     >> xmlbeans.apache.org <http://xmlbeans.apache.org/>
>>>>     >>
>>>>     >>
>>>>     >>
>>>>     >>
>>>>
>>>>
>>>>
>


Mime
View raw message