The biggest issue with GDrive is that our folks in China can’t easily view them ;) My question/feedback comes from the other recent thread about buildpack sizing and efficiency. I did not see a

Because of very good compatibility between versions (post 1.X) I would like to make a motion to do the following: Split the buildpack: have the default golang buildpack track the latest golang

Hi all, We held the first Buildpacks PMC meeting today; I'd like to share the agenda and notes. For reference, all agendas notes for the Buildpacks PMC will be kept in a public Google Drive folder

the go community tends to move fast to adopt the latest versions of go. i imagine we can drop 1.1 and 1.2 without impacting most people. anyone on the list experience otherwise? onsi

Hi Wayne, wayneeseguin(a)starkandwayne.com> wrote: Thanks for asking this question. Currently we're including the following binary dependencies in `go-buildpack`: ``` cache $ ls -lSh

What an incredible step in the right direction, Awesome!!! Out of curiosity, why is the go buildpack still quite so large?

Skinny buildpacks have been cut for go, nodejs, php, python and ruby buildpacks. | | current | previous | |--------+---------+----------| | go | 442MB | 633MB | | nodejs | 69MB |

+1 - I miss the link at the bottom too. Dan

there is, but it would be nicer if the link appeared in the email http://lists.cloudfoundry.org/pipermail/cf-dev/2015-April/000002.html wrote:

Is there a way to link to individual email threads with the new mailing list format? Thanks! Quinn

Hi, I created a few tools to debug OOM problems since the application I was responsible for running on CF was failing constantly because of OOM problems. The problems I had, turned out not to be

Dave, I've found using SSH tunnels can make debugging the JVM easier. I haven't tried using Yourkit via a tunnel, but I suspect it would work. Maybe worth a try. Some more details on setting up