[Mono-dev] Mono release headsup

[arocholl]

I saw that – thank you guys, this is really going to make a difference for IoT with Mono.


Best Regards,
----
Ariel Rocholl



From: Rodrigo Kumpera [mailto:kumpera at gmail.com] 
Sent: Wednesday, February 25, 2015 21:20
To: Ariel Rocholl
Cc: mono-devel-list at lists.ximian.com; Mono List
Subject: Re: [Mono-dev] Mono release headsup

 

Miguel merged a fix for that. I just cherry picked it to 4.0.

 

 

 

On Tue, Feb 24, 2015 at 12:26 PM, Ariel Rocholl <publico at arocholl.com <mailto:publico at arocholl.com> > wrote:

Great – hopefully he is still around and can answer. Otherwise which option B can work? Can I do a minor modification and re-submit as myself fix?


Or alternatively, at least add 250000 and 500000 which are IoT common baudrates not currently included?

 

Best Regards,
----
Ariel Rocholl

 

From: Rodrigo Kumpera [mailto:kumpera at gmail.com <mailto:kumpera at gmail.com> ] 
Sent: Tuesday, February 24, 2015 16:30
To: Ariel Rocholl
Cc: mono-devel-list at lists.ximian.com <mailto:mono-devel-list at lists.ximian.com> ; Mono List
Subject: Re: [Mono-dev] Mono release headsup

 

The patch looks ok, but for it to be merge it must be released under the MIT license, so the author will have to do it.

 

 

 

On Tue, Feb 24, 2015 at 4:52 AM, Ariel Rocholl <publico at arocholl.com <mailto:publico at arocholl.com> > wrote:

Hi there,

 

Could the fix proposed for bug #8207 be considered for the release? This was proposed long ago but didn't progress, and recent renewed interest on high speed custom baud serial communication is required by all IoT gadgets and sort. We are not being able to propose Mono for IoT just because of this, and fix seems really easy to propagate.




Best Regards,
----
Ariel Rocholl

 

On Tue, Feb 24, 2015 at 1:08 AM, Rodrigo Kumpera <kumpera at gmail.com <mailto:kumpera at gmail.com> > wrote:

Hello everyone,

 

We're branching mono for next release as we speak.

 

We'll be able to easily merge community PR until March 6. After that it will have to go through our

internal QA process, which raises the bar a lot and only release blockers can get in.

 

I'll be handling the intake of community changes for the release so make sure I'm aware of any PR targeting it to increase their likelihood of been included.

 

--

Rodrigo

 

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com <mailto:Mono-devel-list at lists.ximian.com> 
http://lists.ximian.com/mailman/listinfo/mono-devel-list

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20150225/e81d2e7b/attachment-0001.html>