[
https://issues.apache.org/jira/browse/SLIDER-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Hao updated SLIDER-757:
Description:
To add this feature would be good for some application that would use extra
resources:
* set
+1
* Checked signatures
* Built from source
* Ran test suite
On Thu, Jan 29, 2015 at 3:00 PM, Josh Elser wrote:
> +1 (binding)
>
> * Filenames have -incubating
> * Xsums+sigs check out
> * KEYS has signing key
> * Built from source
> * Tarballs have LICENSE/NOTICE/DISCLAIMER
> * Looked over th
Greetings, {podling} developers,
The "marvin" automated report reminder script didn't fire for whatever
reason this week, so I'm sending out a bulk reminder manually for the 19
podlings who are expected to submit a February 2015 report. Boilerplate
repinder text below.
Best,
Marvin Humphrey
--
+1 (binding)
* Filenames have -incubating
* Xsums+sigs check out
* KEYS has signing key
* Built from source
* Tarballs have LICENSE/NOTICE/DISCLAIMER
* Looked over third-party licenses
Steve Loughran wrote:
This is a call for a vote on Apache Slider 0.61.0-incubating release
This is a source+b
[
https://issues.apache.org/jira/browse/SLIDER-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated SLIDER-743:
-
Attachment: SLIDER-743.patch
> Include node failure history when choosing placement hints
> --
[
https://issues.apache.org/jira/browse/SLIDER-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297769#comment-14297769
]
ASF subversion and git services commented on SLIDER-734:
Commit 44
+1
Billie Rinaldi wrote:
+1. I think "notifications" is the traditional name. I see some projects
have "issues". Accumulo was not given any leeway on the name ... but you
could try asking for something else. :-)
On Thu, Jan 29, 2015 at 10:35 AM, Steve Loughran
wrote:
A migration to outlo
FYI. I pushed all the accumulated changes just now for publish.
On Thu, Jan 29, 2015 at 11:50 AM, Billie Rinaldi
wrote:
> It should rebuild the staging site (http://slider.staging.apache.org/),
> but
> then you have to publish that to the production site.
>
> On Thu, Jan 29, 2015 at 11:29 AM, St
+1. I think "notifications" is the traditional name. I see some projects
have "issues". Accumulo was not given any leeway on the name ... but you
could try asking for something else. :-)
On Thu, Jan 29, 2015 at 10:35 AM, Steve Loughran
wrote:
> A migration to outlook web access today has br
It should rebuild the staging site (http://slider.staging.apache.org/), but
then you have to publish that to the production site.
On Thu, Jan 29, 2015 at 11:29 AM, Steve Loughran
wrote:
> ?I'd thought that when I committed something to the site svn that triggers
> a rebuild -but it doesn't, does
You can do it at https://cms.apache.org/slider/publish
From: Steve Loughran
Sent: Thursday, January 29, 2015 11:29 AM
To: Slider Dev
Subject: how do I push out a new site?
?I'd thought that when I committed something to the site svn that triggers a
rebuil
Steve,
I think exposing perhaps "instance id" in agent api should be good enough.
I don't think people need full override policy for configuration of every
instance.
Moreover, do you preserve locations for each instance? For a service like
kafka, it writes data to local disk. You can not really s
[
https://issues.apache.org/jira/browse/SLIDER-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved SLIDER-772.
---
Resolution: Fixed
> add sample slider-server.xml with metrics configuration
>
?I'd thought that when I committed something to the site svn that triggers a
rebuild -but it doesn't, does it?
What do I have to do to get the slider web site rebuilt?
[
https://issues.apache.org/jira/browse/SLIDER-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated SLIDER-768:
--
Fix Version/s: Slider 0.70
Assignee: Steve Loughran
Remaining Estimate: 2h
[
https://issues.apache.org/jira/browse/SLIDER-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated SLIDER-641:
--
Sprint: Slider December #1, Slider Jan #2 (was: Slider December #1)
> multiple slider-agent tar
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved SLIDER-737.
---
Resolution: Fixed
Fix Version/s: Slider 0.70
> add LANG=en_US when executing shell comm
On Jan 29, 2015, at 1:35 PM, Steve Loughran wrote:
> A migration to outlook web access today has brought home how much
> machine-generated noise there is in this, primarily JIRA notifying of commits
> and changes.. Gmail had been hiding a lot of this for me.
>
>
> I think this noise is getti
A migration to outlook web access today has brought home how much
machine-generated noise there is in this, primarily JIRA notifying of commits
and changes.. Gmail had been hiding a lot of this for me.
I think this noise is getting in the way of any conversations in the list
itself.
I'm goin
don't worry, we've all done it. It's why my hadoop development corner of my FS
only has read access to the ASF hadoop-common repository, with write access
somewhere else I can only push to when I want to apply a patch
From: Josh Elser
Sent: 29 January 2
[
https://issues.apache.org/jira/browse/SLIDER-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated SLIDER-772:
--
Summary: add sample slider-server.xml with metrics configuration (was: add
sample slider-server
[
https://issues.apache.org/jira/browse/SLIDER-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated SLIDER-772:
--
Summary: add sample slider-server.xml (was: add empty slider-server.xml)
> add sample slider-se
[
https://issues.apache.org/jira/browse/SLIDER-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved SLIDER-752.
---
Resolution: Fixed
> No easy way to get list of applications via API from SliderClient
> --
[
https://issues.apache.org/jira/browse/SLIDER-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297180#comment-14297180
]
Steve Loughran commented on SLIDER-752:
---
And this is what it looks like in the clien
[
https://issues.apache.org/jira/browse/SLIDER-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297176#comment-14297176
]
ASF subversion and git services commented on SLIDER-752:
Commit 7e
Ok, wasn't bad. Should be back to normal
I was trying to update my github (which still had hoya-references) and I
forgot to specify the remote name. Sorry if I caused anyone problems.
Please let me know if I left something borked.
Josh Elser wrote:
I just force-pushed to Apache. Am working o
[
https://issues.apache.org/jira/browse/SLIDER-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297171#comment-14297171
]
ASF subversion and git services commented on SLIDER-766:
Commit af
[
https://issues.apache.org/jira/browse/SLIDER-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297170#comment-14297170
]
ASF subversion and git services commented on SLIDER-759:
Commit 03
[
https://issues.apache.org/jira/browse/SLIDER-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297172#comment-14297172
]
ASF subversion and git services commented on SLIDER-767:
Commit 39
[
https://issues.apache.org/jira/browse/SLIDER-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297167#comment-14297167
]
ASF subversion and git services commented on SLIDER-756:
Commit 96
[
https://issues.apache.org/jira/browse/SLIDER-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297164#comment-14297164
]
ASF subversion and git services commented on SLIDER-723:
Commit 65
[
https://issues.apache.org/jira/browse/SLIDER-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297163#comment-14297163
]
ASF subversion and git services commented on SLIDER-755:
Commit 65
[
https://issues.apache.org/jira/browse/SLIDER-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297165#comment-14297165
]
ASF subversion and git services commented on SLIDER-767:
Commit f5
[
https://issues.apache.org/jira/browse/SLIDER-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297168#comment-14297168
]
ASF subversion and git services commented on SLIDER-769:
Commit 61
[
https://issues.apache.org/jira/browse/SLIDER-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297169#comment-14297169
]
ASF subversion and git services commented on SLIDER-743:
Commit 31
I just force-pushed to Apache. Am working on fixing...
[
https://issues.apache.org/jira/browse/SLIDER-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297140#comment-14297140
]
Steve Loughran commented on SLIDER-752:
---
This is what I've added —will it work?
in
I would favor the current mapping - a little more intuitive IMHO
On Jan 29, 2015, at 5:40 AM, Steve Loughran wrote:
>
> (apologies for any formatting confusion here; I am migrating to Outlook web
> apps)
>
>
> I quite like the git flow bit of the sourcetree GUI; it looks like we can
> chang
Please don't consider my comments more than just comments :)
Just providing my view on the world, but I am by no means intending to
create an impasse.
Totally agree on less branches though :D
Sumit Mohanty wrote:
If we are in an impasse, then lesser branches to manage is better :-)
-Sumit
_
I see. There's configuration per component type, but not per instance of that
type.
That's an interesting idea...I'll have to think about a way that could be made
to work
From: 杨浩
Sent: 28 January 2015 00:45
To: dev@slider.incubator.apache.org
Subject:
(apologies for any formatting confusion here; I am migrating to Outlook web
apps)
I quite like the git flow bit of the sourcetree GUI; it looks like we can
change the policy here for it to make the "master" branch the one git flow
branches from/merges with, "master" could be "release" -and ig
41 matches
Mail list logo
