[Mono-dev] Mono 3.6 release?

[Bob Summerwill]

I would be delighted to contribute all of these Tizen changes back to
Xamarin, including reassigning copyright of all the build scripts and VM
building.

I would also be happy to pay for any VMs and storage capacity which you
need to carry that.  Ditto for hardware costs for ARM on Linux.

Cheers,
Bob
On Jul 31, 2014 9:30 AM, "Bob Summerwill" <bob at summerwill.net> wrote:

> Would that be the case even if all changes were already upstreamed to
> master?
>
> Because that is practically already the case with Tizen.  There was only
> one #ifdef change to the Mono Runtime.   The only other up- streaming still
> todo relates to fixes for pre-existing Linux ARM broken tests or Tizen
> build scripts.
>
> Tizen really is just another Linux distro.  We're just building and
> hosting binaries.
>
> Why not have a "community supported, use at your own risk" section on the
> Downloads page?
>
> Cheers,
> Bob
> On Jul 31, 2014 9:21 AM, "Miguel de Icaza" <miguel at xamarin.com> wrote:
>
>> Hello Bob,
>>
>> In general, I do not link to external packages.  We only link to external
>> packages of established communities and maintainers (like Debian, or
>> Fedora).
>>
>> The only way Tizen is going to get listed on our site is when we build
>> those packages ourselves.
>>
>> Miguel
>>
>>
>> On Wed, Jul 30, 2014 at 12:41 PM, Bob Summerwill <bob at summerwill.net>
>> wrote:
>>
>>> That's what I thought, Miguel.
>>>
>>> Thanks for the clarification.
>>>
>>> With regard to the Tizen RPMs, should I just log a Bugzilla ticket to
>>> get a link added to the Mono Project downloads Web page when 3.6 gets
>>> released?   Thanks.
>>>
>>> Cheers,
>>> Bob
>>> On Jul 30, 2014 9:23 AM, "Miguel de Icaza" <miguel at xamarin.com> wrote:
>>>
>>>> Hello Bob,
>>>>
>>>> No, there is no public process for what we do.   But you can keep an
>>>> eye on the bugs going into Bugzilla, the commits in GitHub and the
>>>> discussions on IRC.
>>>>
>>>>  Miguel
>>>>
>>>>
>>>> On Wed, Jul 30, 2014 at 11:00 AM, Bob Summerwill <bob at summerwill.net>
>>>> wrote:
>>>>
>>>>>
>>>>> I'm not in a rush.   I'm just trying to coordinate release of matching
>>>>> Mono-3.6.0 RPMs for Tizen in an information vacuum.
>>>>>
>>>>> As Alex says, there appears to be no community-visible way to see what
>>>>> the outstanding issues with 3.6 are, and hence judge how close to release
>>>>> we may be.
>>>>>
>>>>> None of this is "a big deal" ... I was just wondering whether there
>>>>> was a community-visible process which I was unaware of other than "It will
>>>>> be done when it is done"?
>>>>>
>>>>>
>>>>> Cheers,
>>>>> Bob
>>>>>
>>>>>
>>>>> On Wed, Jul 30, 2014 at 7:26 AM, Edward Ned Harvey (mono) <
>>>>> edward.harvey.mono at clevertrove.com> wrote:
>>>>>
>>>>>> > From: mono-devel-list-bounces at lists.ximian.com [mailto:
>>>>>> mono-devel-list-
>>>>>> > bounces at lists.ximian.com] On Behalf Of Miguel de Icaza
>>>>>> >
>>>>>> > If you are in a rush, use a git checkout.
>>>>>>
>>>>>> Or just use whatever is the latest stable release, namely 3.4.0?
>>>>>>  Unless there's a specific feature you need, there will *always* be a
>>>>>> pending release, so it normally doesn't make sense to wait for the next
>>>>>> pending release, but instead, normally it makes the most sense to use
>>>>>> whatever the current release is.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> bob at summerwill.net
>>>>>
>>>>>
>>>>
>>
>> _______________________________________________
>> Mono-devel-list mailing list
>> 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/20140731/43344eff/attachment.html>