[
https://issues.apache.org/jira/browse/SLIDER-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959310#comment-14959310
]
Sherry Guo commented on SLIDER-949:
---
Thanks Josh!
> Fix typos on Slider
a slight alteration on the first diff to avoid saying "as it may take
time" twice in the same sentence).
The production site should be up to date (shift-reload if you don't see it
updated). Let us know if you find anything else wrong.
> Fix typos
mmit 1708722 from [~elserj] in branch 'site/trunk'
[ https://svn.apache.org/r1708722 ]
SLIDER-949 Resource Specification doc fixes (Sherry Guo)
> Fix typos on Slider website
>
>
> Key: SLIDER-949
> URL: https://
t the repository, edit the files
locally, and attach a diff to a ticket. Thanks for finding some fixes for
our documentation! Feel free to open a new ticket for that.
Billie
On Tue, Oct 13, 2015 at 11:25 AM, Sherry G
wrote:
> Hi,I have been reading the Slider website, in particular,
[
https://issues.apache.org/jira/browse/SLIDER-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sherry Guo updated SLIDER-949:
--
Attachment: SLIDER-949-001.patch
> Fix typos on Slider webs
[
https://issues.apache.org/jira/browse/SLIDER-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sherry Guo updated SLIDER-949:
--
Summary: Fix typos on Slider website (was: Fix typo Slider website )
> Fix typos on Slider webs
Sherry Guo created SLIDER-949:
-
Summary: Fix typo Slider website
Key: SLIDER-949
URL: https://issues.apache.org/jira/browse/SLIDER-949
Project: Slider
Issue Type: Documentation
2015 at 11:25 AM, Sherry G
wrote:
> Hi,I have been reading the Slider website, in particular,
> https://slider.incubator.apache.org/docs/configuration/resources.html,
> and found a few minor typos. Are the website sources kept in git?
> 1. Slider reacts to a failed container by
Hi,I have been reading the Slider website, in particular,
https://slider.incubator.apache.org/docs/configuration/resources.html, and
found a few minor typos. Are the website sources kept in git?
1. Slider reacts to a failed container by requesting a new container from YARN,
preferably on a
[
https://issues.apache.org/jira/browse/SLIDER-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billie Rinaldi resolved SLIDER-121.
---
Resolution: Fixed
> Convert Slider website to
mmit 1612872 from [~billie.rinaldi]
[ https://svn.apache.org/r1612872 ]
SLIDER-121 remove manually generated site content
> Convert Slider website to CMS
> -
>
> Key: SLIDER-121
> URL: https://issues.apache.org/jir
mmit 1609861 from smoha...@apache.org
[ https://svn.apache.org/r1609861 ]
SLIDER-121 manually generate slider site from CMS content for now (preparation
for next release)
> Convert Slider website to CMS
> -
>
> Key: SLIDER-121
>
mmit 1609860 from smoha...@apache.org
[ https://svn.apache.org/r1609860 ]
SLIDER-121 manually generate slider site from CMS content for now (preparation
for next release)
> Convert Slider website to CMS
> -
>
> Key: SLIDER-121
>
mmit 1609845 from smoha...@apache.org
[ https://svn.apache.org/r1609845 ]
SLIDER-121 manually generate slider site from CMS content for now (preparation
for next release)
> Convert Slider website to CMS
> -
>
> Key: SLIDER-121
>
mmit 1609636 from smoha...@apache.org in branch 'site/trunk'
[ https://svn.apache.org/r1609636 ]
SLIDER-121 manually generate slider site from CMS content for now (preparation
for next release)
> Convert Slider website to CMS
> -
>
>
mmit 1609637 from smoha...@apache.org
[ https://svn.apache.org/r1609637 ]
SLIDER-121 manually generate slider site from CMS content for now (preparation
for next release)
> Convert Slider website to CMS
> -
>
> Key: SLIDER-121
>
mmit 1609635 from smoha...@apache.org
[ https://svn.apache.org/r1609635 ]
SLIDER-121 manually generate slider site from CMS content for now (preparation
for next release)
> Convert Slider website to CMS
> -
>
> Key: SLIDER-121
>
mmit 1609634 from smoha...@apache.org in branch 'site/trunk'
[ https://svn.apache.org/r1609634 ]
SLIDER-121 manually generate slider site from CMS content for now (preparation
for next release)
> Convert Slider website to CMS
> -
>
>
mmit 1609347 from smoha...@apache.org in branch 'site/trunk'
[ https://svn.apache.org/r1609347 ]
SLIDER-121 manually generate slider site from CMS content for now (preparation
for next release)
> Convert Slider website to CMS
> -
>
>
mmit 1608675 from smoha...@apache.org in branch 'site/trunk'
[ https://svn.apache.org/r1608675 ]
SLIDER-121 manually generate slider site from CMS content for now (preparation
for next release)
> Convert Slider website to CMS
> -
>
>
mmit 1608633 from smoha...@apache.org
[ https://svn.apache.org/r1608633 ]
SLIDER-121 manually generate slider site from CMS content for now
> Convert Slider website to CMS
> -
>
> Key: SLIDER-121
> URL: https://issues.apa
mmit 1608561 from [~billie.rinaldi]
[ https://svn.apache.org/r1608561 ]
SLIDER-121 manually generate slider site from CMS content for now
> Convert Slider website to CMS
> -
>
> Key: SLIDER-121
> URL: https://issues.apa
mmit 209cee43355b943dd55f368ee55a5234ebc3e54b in incubator-slider's branch
refs/heads/develop from [~billie.rina...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=209cee4 ]
SLIDER-121 removed site documentation from git source
> Convert Slider we
[
https://issues.apache.org/jira/browse/SLIDER-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billie Rinaldi updated SLIDER-121:
--
Description: See also INFRA-7954.
> Convert Slider website to
mmit 1605167 from [~billie.rinaldi] in branch 'site/trunk'
[ https://svn.apache.org/r1605167 ]
SLIDER-121 check in initial CMS-ready website based on original maven site
documentation
> Convert Slider website to CMS
> -
>
>
Billie Rinaldi created SLIDER-121:
-
Summary: Convert Slider website to CMS
Key: SLIDER-121
URL: https://issues.apache.org/jira/browse/SLIDER-121
Project: Slider
Issue Type: Improvement
On May 5, 2014, at 4:33 PM, Jon Maron wrote:
> I’ve made some updates to the current site code in its current location.
> Given that CMS/infra is expecting the site source to be in
> https://svn.apache.org/repos/asf/incubator/slider/site/, it would appear that
> this directory would require
They've changed the website urls, but not all of the documentation yet.
The right url should be slider.i.a.o.
On Mon, May 5, 2014 at 2:23 PM, Jon Maron wrote:
>
> On May 5, 2014, at 4:33 PM, Jon Maron wrote:
>
> > I’ve made some updates to the current site code in its current location.
> Give
On May 5, 2014, at 4:33 PM, Jon Maron wrote:
> I’ve made some updates to the current site code in its current location.
> Given that CMS/infra is expecting the site source to be in
> https://svn.apache.org/repos/asf/incubator/slider/site/, it would appear that
> this directory would require
I’ve made some updates to the current site code in its current location. Given
that CMS/infra is expecting the site source to be in
https://svn.apache.org/repos/asf/incubator/slider/site/, it would appear that
this directory would require someone to create a local commit that:
1) adds a pom.x
On May 5, 2014, at 11:47 AM, Josh Elser wrote:
> On 5/5/14, 11:30 AM, Jon Maron wrote:
>> On May 5, 2014, at 11:09 AM, Josh Elser wrote:
>>
>>> >Ah, ok. How doeshttp://people.apache.org/~elserj/slider/site/ look for
>>> >starters?
>> I’ve been iterating through this as well and made some cha
On 5/5/14, 11:30 AM, Jon Maron wrote:
On May 5, 2014, at 11:09 AM, Josh Elser wrote:
>Ah, ok. How doeshttp://people.apache.org/~elserj/slider/site/ look for
starters?
I’ve been iterating through this as well and made some changes:
- announcement.html - doesn’t actually exist. for the time
;>>>> On 5/2/14, 12:52 PM, Jon Maron wrote:
>>>>>>>> The other alternative is to forego the CMS and:
>>>>>>>>
>>>>>>>> 1) Manually login to people.apache.org
>>>>>>>> 2) create the web root
On 5/5/14, 11:16 AM, Josh Elser wrote:
On 5/5/14, 11:08 AM, Jon Maron wrote:
On May 5, 2014, at 10:40 AM, Josh Elser wrote:
On 5/5/14, 9:52 AM, Jon Maron wrote:
On May 5, 2014, at 9:19 AM, Steve Loughran
wrote:
OK, to make life more complicated, we can't use svnpubsub and
git, so if
we s
On 5/5/14, 11:08 AM, Jon Maron wrote:
On May 5, 2014, at 10:40 AM, Josh Elser wrote:
On 5/5/14, 9:52 AM, Jon Maron wrote:
On May 5, 2014, at 9:19 AM, Steve Loughran wrote:
OK, to make life more complicated, we can't use svnpubsub and git, so if
we switch to git, then we have to use CMS
correct args to the perl script gives no indication as to how that
process
actually works - do we invoke the script to build a new site, do we
somehow
configure CMS to execute the script periodically or manually, etc)
-- Jon
On May 2, 2014, at 11:44 AM, Billie Rinaldi <
billie.rina...@gm
On May 5, 2014, at 10:40 AM, Josh Elser wrote:
> On 5/5/14, 9:52 AM, Jon Maron wrote:
>> On May 5, 2014, at 9:19 AM, Steve Loughran wrote:
>>
>>> >OK, to make life more complicated, we can't use svnpubsub and git, so if
>>> >we switch to git, then we have to use CMS
>>> >
>>> >Having been bac
On 5/5/14, 9:52 AM, Jon Maron wrote:
On May 5, 2014, at 9:19 AM, Steve Loughran wrote:
>OK, to make life more complicated, we can't use svnpubsub and git, so if
>we switch to git, then we have to use CMS
>
>Having been back in svn for a couple of days, I'm missing some of the git
>features, n
ite
>>>>>> provides. Maybe there's some middle ground that we can do that we can
>>>> reach
>>>>>> that encapsulates some of the existing documentation from Github?
>>>>>>>
>>>>>>> On 5/2/14, 12:52 PM,
Jon Maron wrote:
>> > >>>> The other alternative is to forego the CMS and:
>> > >>>>
>> > >>>> 1) Manually login to people.apache.org
>> > >>>> 2) create the web root directory for the project
>> >
t;>>> 4) From that point on essentially use 'svn update' to update the
> site
> > >> when sources are changed
> > >>>>
> > >>>> I think I like the idea of using the CMS approach, I'm just not
> > certain
> > >> how it's actual
re us to add the generated files to svn)
> >>>> 4) From that point on essentially use 'svn update' to update the site
> >> when sources are changed
> >>>>
> >>>> I think I like the idea of using the CMS approach, I'm just not
ite
>> when sources are changed
>>>>
>>>> I think I like the idea of using the CMS approach, I'm just not certain
>> how it's actually implemented (the one sentence indicating providing the
>> correct args to the perl script gives no indicatio
ike the idea of using the CMS approach, I'm just not certain
> how it's actually implemented (the one sentence indicating providing the
> correct args to the perl script gives no indication as to how that process
> actually works - do we invoke the script to build a new site, do
invoke the script to build a new site, do we somehow configure
>> CMS to execute the script periodically or manually, etc)
>>
>> -- Jon
>>
>> On May 2, 2014, at 11:44 AM, Billie Rinaldi wrote:
>>
>>> Regarding the imminent creation of our Slider
tually
>> works - do we invoke the script to build a new site, do we somehow configure
>> CMS to execute the script periodically or manually, etc)
>>
>> -- Jon
>>
>> On May 2, 2014, at 11:44 AM, Billie Rinaldi wrote:
>>
>>> Regarding the imminent creation
1:44 AM, Billie Rinaldi wrote:
Regarding the imminent creation of our Slider website, it seems that CMS is
capable of building a site using Maven:
https://www.apache.org/dev/cmsref.html#external-build
http://svn.apache.org/repos/asf/maven/site/trunk/content
which is great, because that means we&#x
is built to a staging area first, so
you can inspect the changes, and then you can publish to the production
site.
>
> -- Jon
>
> On May 2, 2014, at 11:44 AM, Billie Rinaldi
> wrote:
>
> > Regarding the imminent creation of our Slider website, it seems that CMS
> is
>
ually
works - do we invoke the script to build a new site, do we somehow configure
CMS to execute the script periodically or manually, etc)
-- Jon
On May 2, 2014, at 11:44 AM, Billie Rinaldi wrote:
> Regarding the imminent creation of our Slider website, it seems that CMS is
> capable of b
Regarding the imminent creation of our Slider website, it seems that CMS is
capable of building a site using Maven:
https://www.apache.org/dev/cmsref.html#external-build
http://svn.apache.org/repos/asf/maven/site/trunk/content
which is great, because that means we'd be able to edit mar
50 matches
Mail list logo
