[Mono-dev] Mono 3.6 release?

[Bob Summerwill]

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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20140730/e6c3803a/attachment.html>