Hi Jonathan,
Thanks for taking the time to provide the background.
I understand/agree that facilitating development on Windows is a complex
task. I've seen some of the emails over time and can well imagine it's
complex and invasive to the existing build system. People start the
work, but I''ve
Hi Guys,
I took it upon myself to try and get a build up and running on Appveyor
yesterday. Please have a look at https://github.com/mika76/mono and
https://ci.appveyor.com/project/mmihajlovic/mono - so far the only thing
I've edited is the appveyor.yml file and the actual a[[veyor settings.
At
Hi Mladen,
Sounds good to me. I've not encountered Appveyor before but it looks
good. How do you get the Cygwin dependencies in there? Can it be assumed
that what's happening in the Appveyor build is basically the same as on
a standard Windows box?
Cheers,
Alex
On 17/10/2014 08:53, Mladen
Hey Alex
There's a lot that you can do through their yml settings file. Download and
setup pretty much anything. Have a look in the root if the repo:
appveyor.yml.
On 17 Oct 2014 8:59 AM, Alex J Lennon ajlen...@dynamicdevices.co.uk
wrote:
Hi Mladen,
Sounds good to me. I've not encountered
On 17/10/14 03:52, David Nelson wrote:
...my observations have not convinced me
that such contributions would be an effective use of my time.
Did your observations include only unmerged pull requests, or did you
also happen to check how many of them get merged? The latter is
important too.
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Bryan Crotaz
Who's with me?
FWIW, the state of mono for windows is really really bad, but it's not great
for rhel or ubuntu either. I agree *enormously* that there's a big
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Martin Thwaites
Just to give my2cents on this.
I would just like to know that things will get looked at approved at some
point.
Getting reviewed is one thing. (Difficult
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Edward Ned Harvey (mono)
Getting reviewed is one thing. (Difficult enough.) Getting approved is a
completely different thing - even more perilous.
... etc etc yadda yadda ...
On 17/10/2014 16:07, Alex J Lennon wrote:
On 17/10/2014 09:09, Mladen Mihajlovic wrote:
Hey Alex
There's a lot that you can do through their yml settings file.
Download and setup pretty much anything. Have a look in the root if
the repo: appveyor.yml.
Hi Mladen,
I like the look of
Hi,
We were helping someone who was having performance problems with a large
streaming application that they run under .NET and mono. On .NET the app
takes around 7-10 seconds to do its stuff. On Mono on Linux it was taking
47 seconds or so to do the same thing. The mono system had 256G RAM and
Disclaimer: I know nothing about these classes.
That said, I firmly support the plan to bring PRs into the mailing list,
and would hate to see such a great plan get no love, so I want to say that
from looking at these (very small and easily digested) changes, they at
least look clean and good.
Thanks Chris,
The main thing I think will be off benefit with people reviewing is simply
getting that second pair of eyes to sanity check it. Looking for basic
coding standards stuff, anything obvious. Other things like advice on
separating things out etc.
On 17 October 2014 20:46, Chris Rogus
This might have gotten buried in the other thread. So here's a new thread to
bring it up to attention.
Miguel, this question is probably for you. (And by the way, thank you for
everything, and especially thank you for participating here.)
The bottleneck that's preventing much community
Hello,
The build bot does some of this work when you submit a pull request. It
does not cover all platforms, nor all configurations, but it is a good
first step.
But this is not a problem. Not every patch affects all systems, and most
of the code is cross platform, so testing on one is
Hi All,
This is probably more a question for Miguel, but I thought I'd make it
public.
I'm looking through the list of PR's (103 at the moment) and I thought it
best to go from the end. However, it seems like most of these are either
done by someone who no longer has interest in contributing,
For this to work, I'm thinking we (I'm happy to dedicate some time to
this) could just ping the mailing list to ask you close them Miguel? I'm
thinking it's an easy and quick thing to do, so we can expect a fairly
quick turnaround?
I dont think they hurt to keep them open.
Do not want to
Thanks Miguel,
I appreciate why you would want to keep them, however, do you not feel the
list is currently unmanageable?
Maybe we could add labels (the ones in GitHub, not used them before but it
looks like it could work) to the older ones like inactive so we know
which ones are worth reviewing
I would like to add that, on the Metasploit framework, we often have 80+
pull requests open at any given point in time, and labels in Github are
*so* useful.
https://github.com/rapid7/metasploit-framework/pulls
On Fri, Oct 17, 2014 at 5:27 PM, Martin Thwaites monofo...@my2cents.co.uk
wrote:
18 matches
Mail list logo
