Unsubscribe
On Sep 15, 2015 11:27 PM, "Alex Harui" wrote:
> On 7/16/15, 7:24 AM, "Alex Harui" wrote:
>
> >OK. Thanks for the info.
> >
> >I might try subsetting the information to not grab the release info and
> >run a job once a day to cache the latest for my project on some other
> >server.
On 7/16/15, 7:24 AM, "Alex Harui" wrote:
>OK. Thanks for the info.
>
>I might try subsetting the information to not grab the release info and
>run a job once a day to cache the latest for my project on some other
>server. I’ll reply back on this thread if I ever get it working.
>
>-Alex
OK, I
> Any list containing either "commits", "private" or "security" is left out
of the generated report template for privacy and s2n ratio issues.
Makes sense, thanks for the explanation.
-- Lefty
On Thu, Jul 16, 2015 at 10:24 AM, Alex Harui wrote:
> OK. Thanks for the info.
>
> I might try subs
OK. Thanks for the info.
I might try subsetting the information to not grab the release info and
run a job once a day to cache the latest for my project on some other
server. I’ll reply back on this thread if I ever get it working.
-Alex
On 7/16/15, 6:29 AM, "Rich Bowen" wrote:
>
>
>On 05/01
On 05/01/2015 05:32 PM, Alex Harui wrote:
This is a really cool service. I noticed it wants login creds. What data
would have to be stripped in order to allow general public access? What
would it take to get the JSON for the public info? I’ll write the client
side in Apache Flex.
In addit
On 1 May 2015 at 22:32, Alex Harui wrote:
> This is a really cool service. I noticed it wants login creds.
Creds are needed in order to validate updating of release data.
> What data
> would have to be stripped in order to allow general public access?
I don't know.
> What
> would it take to
On 16 July 2015 at 11:47, Daniel Gruno wrote:
> Hi Lefty,
> Any list containing either "commits", "private" or "security" is left out
> of the generated report template for privacy and s2n ratio issues.
> This is partly because the reports will be publicly available, and partly
> because a disint
Hi Lefty,
Any list containing either "commits", "private" or "security" is left
out of the generated report template for privacy and s2n ratio issues.
This is partly because the reports will be publicly available, and
partly because a disinterest was expressed in having commits@ stats, as
that
Question about the report template: why doesn't it include the commits@
mailing list? (Is that because JIRA activity already covers the number of
commits?)
Thanks.
-- Lefty
On Fri, May 1, 2015 at 5:32 PM, Alex Harui wrote:
> This is a really cool service. I noticed it wants login creds.
This is a really cool service. I noticed it wants login creds. What data
would have to be stripped in order to allow general public access? What
would it take to get the JSON for the public info? I’ll write the client
side in Apache Flex.
Thanks,
-Alex
On 3/5/15, 1:39 AM, "Daniel Gruno" wrot
On 03/03/2015 06:04 PM, Lefty Leverenz wrote:
Kudos, Daniel! Great idea.
Question 1: How can RMs add release data if they aren't PMC members?
(This might be answered by your most recent message.)
Sounds like a great opportunity to vote someone onto your PMC.
--
Rich Bowen - rbo...@rcbow
On 2015-03-05 01:00, sebb wrote:
On 4 March 2015 at 07:26, Daniel Gruno wrote:
On 2015-03-04 01:29, sebb wrote:
The tool looks cool, but does not handle Apache Commons properly, as
it calls it "Apache Commons BeanUtils".
BeanUtils is just one of the Commons components (it seems to be
pickin
On 4 March 2015 at 07:26, Daniel Gruno wrote:
>
>
> On 2015-03-04 01:29, sebb wrote:
>>
>> The tool looks cool, but does not handle Apache Commons properly, as
>> it calls it "Apache Commons BeanUtils".
>> BeanUtils is just one of the Commons components (it seems to be
>> picking the first compone
On 2015-03-04 01:29, sebb wrote:
The tool looks cool, but does not handle Apache Commons properly, as
it calls it "Apache Commons BeanUtils".
BeanUtils is just one of the Commons components (it seems to be
picking the first component alphabetically).
This was due to Commons not having any infor
Le 03/03/2015 23:58, Daniel Gruno a écrit :
On 2015-03-03 23:09, Christopher wrote:
Pretty cool.
A couple of suggestions:
1) if the release dates could be kept up-to-date from versions marked in
JIRA as "released" with a date (
https://issues.apache.org/jira/browse/ACCUMULO/?selectedTab=com.
The tool looks cool, but does not handle Apache Commons properly, as
it calls it "Apache Commons BeanUtils".
BeanUtils is just one of the Commons components (it seems to be
picking the first component alphabetically).
The JIRA release option does not work well for Commons.
Each component has a sep
On 2015-03-04 00:13, Lefty Leverenz wrote:
Way cool! I just tried "Fetch releases from JIRA" and now it shows Hive
releases starting with 0.3.0 in 2009.
great!
One technical glitch, though: release 0.9.0 is near the top of the y-axis
and then 0.10.0 drops down to the bottom. After 0.14.0
Way cool! I just tried "Fetch releases from JIRA" and now it shows Hive
releases starting with 0.3.0 in 2009.
One technical glitch, though: release 0.9.0 is near the top of the y-axis
and then 0.10.0 drops down to the bottom. After 0.14.0 there's a jump up
to the top with 1.0.0.
Apparently the
On 2015-03-04 00:04, Lefty Leverenz wrote:
Kudos, Daniel! Great idea.
Question 1: How can RMs add release data if they aren't PMC members?
(This might be answered by your most recent message.)
They can't, which is why the email sent to people that push to dist says
to contact a PMC member
Kudos, Daniel! Great idea.
Question 1: How can RMs add release data if they aren't PMC members?
(This might be answered by your most recent message.)
Questions 2 & 3: Do the chart timelines advance week-by-week or
month-by-month? How often is the template refreshed? The #emails sent "in
the
On 2015-03-03 23:09, Christopher wrote:
Pretty cool.
A couple of suggestions:
1) if the release dates could be kept up-to-date from versions marked in
JIRA as "released" with a date (
https://issues.apache.org/jira/browse/ACCUMULO/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-
On 2015-03-03 23:09, Christopher wrote:
Pretty cool.
A couple of suggestions:
1) if the release dates could be kept up-to-date from versions marked in
JIRA as "released" with a date (
https://issues.apache.org/jira/browse/ACCUMULO/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-
Pretty cool.
A couple of suggestions:
1) if the release dates could be kept up-to-date from versions marked in
JIRA as "released" with a date (
https://issues.apache.org/jira/browse/ACCUMULO/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel),
that'd be really cool.
2) If the sy
Do note, I just broke the site - it will be another 10 minutes before
it's back up ;)
On 2015-03-03 20:47, Jacques Le Roux wrote:
Le 03/03/2015 19:47, Daniel Gruno a écrit :
On 2015-03-03 18:52, Jacques Le Roux wrote:
Daniel,
Actually trying to add a release I got a 500:
http://www.apache
Le 03/03/2015 19:47, Daniel Gruno a écrit :
On 2015-03-03 18:52, Jacques Le Roux wrote:
Daniel,
Actually trying to add a release I got a 500:
http://www.apache.org/dev/service_unavailable.html?site=reporter.apache.org&code=500
From the logs, I can tell that you supplied an invalid release d
On 2015-03-03 18:52, Jacques Le Roux wrote:
Daniel,
Actually trying to add a release I got a 500:
http://www.apache.org/dev/service_unavailable.html?site=reporter.apache.org&code=500
From the logs, I can tell that you supplied an invalid release date,
which made the script break.
I have adde
On Tue, Mar 3, 2015 at 7:55 AM, Daniel Gruno wrote:
> Hi Jacques,
> I tried to pull in as much information as I could about LDAP changes, but
> sadly, we have not kept track of new committers being added to a project in
> the same way we keep track of PMC additions, hence this behavior on the
> s
Daniel,
Actually trying to add a release I got a 500:
http://www.apache.org/dev/service_unavailable.html?site=reporter.apache.org&code=500
Thanks
Jacques
Le 03/03/2015 18:44, Jacques Le Roux a écrit :
Thanks Daniel,
That's quite clear
Jacques
Le 03/03/2015 16:55, Daniel Gruno a écrit :
Thanks Daniel,
That's quite clear
Jacques
Le 03/03/2015 16:55, Daniel Gruno a écrit :
Hi Jacques,
I tried to pull in as much information as I could about LDAP changes, but sadly, we have not kept track of new committers being added to a project
in the same way we keep track of PMC additions,
Hi Jacques,
I tried to pull in as much information as I could about LDAP changes,
but sadly, we have not kept track of new committers being added to a
project in the same way we keep track of PMC additions, hence this
behavior on the site. There's no fix for this currently, BUT it will
correct
Thanks Daniel,
That's pretty cool, just as a note, the OFBiz project shows that no committers has been added since September when we had 4 new committers in
December, can we change that?
I will add the releases we have at http://ofbiz.apache.org/download.html
Jacques
Le 03/03/2015 11:50, Da
Wow Daniel this is awesome!!
++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.m
On 2015-03-03 15:10, Rich Bowen wrote:
On 03/03/2015 06:51 AM, Daniel Gruno wrote:
Hi Rob,
If the release you messed up is within the last 3 months, you can just
override it with a fake older date and make it go out of view (add the
release again and set the date to 1970-01-01 for instance).
On 03/03/2015 06:51 AM, Daniel Gruno wrote:
Hi Rob,
If the release you messed up is within the last 3 months, you can just
override it with a fake older date and make it go out of view (add the
release again and set the date to 1970-01-01 for instance). I'll work on
a smarter editing feature so
On 2015-03-03 14:39, Yann Ylavic wrote:
Hi Daniel,
maybe bugs@ and modules-dev@(httpd only?) could go upper too?
Sure thing, consider it done!
With regards,
Daniel.
Anyway, thanks for all this work.
Regards,
Yann.
On Tue, Mar 3, 2015 at 2:08 PM, Daniel Gruno wrote:
Hi Dan,
I have now m
Hi Daniel,
maybe bugs@ and modules-dev@(httpd only?) could go upper too?
Anyway, thanks for all this work.
Regards,
Yann.
On Tue, Mar 3, 2015 at 2:08 PM, Daniel Gruno wrote:
> Hi Dan,
> I have now made the system prefer those list first on the report in that
> order (and any other lists come l
cool. Many thx
Dan
On 3 March 2015 at 13:08, Daniel Gruno wrote:
> Hi Dan,
> I have now made the system prefer those list first on the report in that
> order (and any other lists come later then)
>
> With regards,
> Daniel.
>
>
> On 2015-03-03 13:58, Dan Haywood wrote:
>
>> Nice work, Daniel.
Hi Jan,
This is for TLPs only for the time being - adding podlings is a bit of a
mess due to how we have multiple naming conventions for that data and
the fact that IPMC members would be shown all 36 podlings whenever they
accessed the system ;)
But a workaround is in the works :)
With regar
Hi Dan,
I have now made the system prefer those list first on the report in that
order (and any other lists come later then)
With regards,
Daniel.
On 2015-03-03 13:58, Dan Haywood wrote:
Nice work, Daniel.
request: could the subscribers graphs be in the order of users, dev,
commits, private?
Very nice work indeed.
Any chance, podlings could be included, or do we need try and become pTLP ?
rgds
jan i.
On 3 March 2015 at 13:58, Dan Haywood wrote:
> Nice work, Daniel.
>
> request: could the subscribers graphs be in the order of users, dev,
> commits, private?
>
> Thx
> Dan
>
>
>
> On
Nice work, Daniel.
request: could the subscribers graphs be in the order of users, dev,
commits, private?
Thx
Dan
On 3 March 2015 at 12:42, Daniel Gruno wrote:
> Apologies, I was hacking on that chart while you were watching, it should
> be finished now - it's an attempt at least :)
>
> With
Apologies, I was hacking on that chart while you were watching, it
should be finished now - it's an attempt at least :)
With regards,
Daniel.
On 2015-03-03 13:32, Rob Vesse wrote:
Setting the fake date didn't seem to do the trick and actually broke the
mock up release timeline graphic someone
Setting the fake date didn't seem to do the trick and actually broke the
mock up release timeline graphic someone already hacked in
I like the time line somebody already mocked up though it doesn't display
that nicely in Safari at least. The other thing I was thinking of was a
simple graph simila
Hi Rob,
If the release you messed up is within the last 3 months, you can just
override it with a fake older date and make it go out of view (add the
release again and set the date to 1970-01-01 for instance). I'll work on
a smarter editing feature soon.
Viewing previous release cycles and su
Daniel
This is really cool
Quick question - how do we correct errors in the release data? I just
went through and added all the releases for the PMC of which I am a member
and realised I made a typo in the version number for one of our releases.
Where do I go to correct this?
Also it would be n
45 matches
Mail list logo
