Re: [Mono-dev] [Mono-list] Mono Web Site

[Bob Summerwill]

That is SO much better!

Nice work, guys!


Cheers,
Bob


On Wed, Aug 13, 2014 at 12:35 PM, William Ivanski  wrote:

> Miguel, it is really nice to see the new website! It is cleaner! :)
>
> William Ivanski
>
>
> 2014-08-13 16:26 GMT-03:00 Miguel de Icaza :
>
>> Hello guys,
>>
>> Thanks to the help of Alexander Koeplinger that worked with us for the
>> last couple of months, we have migrated the Mono website from MediaWiki to
>> a static content manager on GitHub.
>>
>> Ideally, this means that we will be able to take pull requests for the
>> web site, and anyone with commit access to Mono can now update the web site.
>>
>> When you commit, the pages are regenerated.
>>
>> The web module is here:
>>
>> https://github.com/mono/website
>>
>> There are still a few details that we need to sort out here and there,
>> but we should be in much better shape.
>>
>> Miguel
>>
>> ___
>> Mono-list maillist  -  mono-l...@lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-list
>>
>>
>
> ___
> Mono-list maillist  -  mono-l...@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
>
>


-- 
b...@summerwill.net
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

[Mono-dev] Mono Web Site

[Miguel de Icaza]

Hello guys,

Thanks to the help of Alexander Koeplinger that worked with us for the last
couple of months, we have migrated the Mono website from MediaWiki to a
static content manager on GitHub.

Ideally, this means that we will be able to take pull requests for the web
site, and anyone with commit access to Mono can now update the web site.

When you commit, the pages are regenerated.

The web module is here:

https://github.com/mono/website

There are still a few details that we need to sort out here and there, but
we should be in much better shape.

Miguel
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Building Roslyn on OS X

[Jeff Kilpatrick]

> None of these do what I suggested. You need to delete folders like
> 
> Src/Compilers/CSharp/Desktop/obj/

That did it. Thanks for your patience!


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Building Roslyn on OS X

[Marek Safar]

Hi,

>
> > You've mostly done it. We have a bug in xbuild which causes this on
> second build. Clean all intermediate obj folders and run xbuild again.
>
> Unfortunately, that didn’t do it for me. I tried a few different cleaning
> options, but I’m still getting the same error:
>
> (*) rm -fr Binaries && xbuild …
> (*) rm Binaries/Debug/Microsoft.CodeAnalysis.* && xbuild … # This is the
> assembly containing the internal classes we’re trying to access; Release
> configs have the same issue
> (*) xbuild /target:clean Src/Compilers/CSharp/csc/csc.csproj && xbuild …
>

None of these do what I suggested. You need to delete folders like

Src/Compilers/CSharp/Desktop/obj/

Marek
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono 3.6 release? (Mono-devel-list Digest, Vol 112, Issue 12)

[Bob Summerwill]

OK - I'll proceed with my own announcement.


Cheers,
Bob


On Wed, Aug 13, 2014 at 9:35 AM, Jo Shields  wrote:

>
> On 08/13/2014 01:47 PM, Bob Summerwill wrote:
>
>> 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.

>>>
>> I guess the non-reply means "no thanks" on both of those offers?
>>
>> The Mono 3.6 Releases Notes page was created about a week ago:
>>
>>  http://www.mono-project.com/Release_Notes_Mono_3.6
>>
>> Xamarin.iOS-7.2.6 which was released about a week ago states "Mono
>> runtime/BCL updated to 3.6":
>>
>>  http://developer.xamarin.com/releases/ios/xamarin.ios_7/
>> xamarin.ios_7.2/
>>
>> As of yesterday the Mono Project downloads page is showing Mono 3.6 links:
>>
>>  http://www.go-mono.com/mono-downloads/download.html
>>
>> Damien notes ...
>>
>>  They did not tag the HEAD of the branch, but an older commit!  But we
>>  already had a set of RPMs based on that, so no rebuild was necessary.
>>  I have updated MonoTizen's gh-pages to point to the matching
>> binaries:
>>  2d7113a..9f8394f  gh-pages -> gh-pages
>>
>> So can we consider Mono 3.6 to be released?Will there be a release
>> announcement today?
>>
>
> Yes, 3.6.0 is released now, I did the uploads yesterday evening. I'm still
> finding my feet on process and procedure for releases but that should
> improve in the coming months.
>
>  I will update the http://monotizen.com page to include links to the Tizen
>> RPMs, and make my own announcement.
>>
>
> In the short term, I think that's the best plan - there's a bucket of
> stuff on my TODO list to help reach a wider Linux-based audience, but I
> don't have the systems and procedures in place right now for anything
> Tizen-related to make sense (there's more to it than just adding some VMs).
>
> You would likely reach the Tizen developer community far more effectively
> than I would, right now. Down the line, as I find my feet more and get the
> underlying structures in place, coordinating becomes much easier.
>



-- 
b...@summerwill.net
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono 3.6 release?

[Bob Summerwill]

Hokey dokey - thanks for the confirmation.


On Wed, Aug 13, 2014 at 9:34 AM, Miguel de Icaza  wrote:

>
>> So can we consider Mono 3.6 to be released?Will there be a release
>> announcement today?
>>
>
> yes, it is released.
>
> We will look into doing the announcement on the blog.
>
> MIguel
>



-- 
b...@summerwill.net
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Building Roslyn on OS X

[Jeff Kilpatrick]

Thanks, Marek.

> You've mostly done it. We have a bug in xbuild which causes this on second 
> build. Clean all intermediate obj folders and run xbuild again.

Unfortunately, that didn’t do it for me. I tried a few different cleaning 
options, but I’m still getting the same error:

(*) rm -fr Binaries && xbuild …
(*) rm Binaries/Debug/Microsoft.CodeAnalysis.* && xbuild … # This is the 
assembly containing the internal classes we’re trying to access; Release 
configs have the same issue
(*) xbuild /target:clean Src/Compilers/CSharp/csc/csc.csproj && xbuild …

Any other ideas or corrections to the cleaning steps?

Thanks,
Jeff

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono 3.6 release? (Mono-devel-list Digest, Vol 112, Issue 12)

[Jo Shields]

On 08/13/2014 01:47 PM, Bob Summerwill wrote:

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.


I guess the non-reply means "no thanks" on both of those offers?

The Mono 3.6 Releases Notes page was created about a week ago:

 http://www.mono-project.com/Release_Notes_Mono_3.6

Xamarin.iOS-7.2.6 which was released about a week ago states "Mono
runtime/BCL updated to 3.6":

 http://developer.xamarin.com/releases/ios/xamarin.ios_7/xamarin.ios_7.2/

As of yesterday the Mono Project downloads page is showing Mono 3.6 links:

 http://www.go-mono.com/mono-downloads/download.html

Damien notes ...

 They did not tag the HEAD of the branch, but an older commit!  But we
 already had a set of RPMs based on that, so no rebuild was necessary.
 I have updated MonoTizen's gh-pages to point to the matching binaries:
 2d7113a..9f8394f  gh-pages -> gh-pages

So can we consider Mono 3.6 to be released?Will there be a release
announcement today?


Yes, 3.6.0 is released now, I did the uploads yesterday evening. I'm 
still finding my feet on process and procedure for releases but that 
should improve in the coming months.



I will update the http://monotizen.com page to include links to the Tizen
RPMs, and make my own announcement.


In the short term, I think that's the best plan - there's a bucket of 
stuff on my TODO list to help reach a wider Linux-based audience, but I 
don't have the systems and procedures in place right now for anything 
Tizen-related to make sense (there's more to it than just adding some VMs).


You would likely reach the Tizen developer community far more 
effectively than I would, right now. Down the line, as I find my feet 
more and get the underlying structures in place, coordinating becomes 
much easier.

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono 3.6 release?

[Miguel de Icaza]

>
>
> So can we consider Mono 3.6 to be released?Will there be a release
> announcement today?
>

yes, it is released.

We will look into doing the announcement on the blog.

MIguel
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono 3.6 release?

[Slide]

FYI, these came through just fine.


On Wed, Aug 13, 2014 at 9:24 AM, Bob Summerwill  wrote:

> It appears that the Forum system blackholed some e-mails from me.   Either
> that, or they are still awaiting "moderator approval" a week later, so
> let's try again ...
>
>
> Jul 31, 2014; 9:30am [image: bobsummerwill][image: online]
> 
>  bobsummerwill
> 
>
> 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
>
>
> Jul 31, 2014; 9:34am [image: bobsummerwill][image: online]
> 
>  bobsummerwill
> 
>
> 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 Wed, Aug 13, 2014 at 5:47 AM, Bob Summerwill 
> wrote:
>
>> >> 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.
>>
>>
>> I guess the non-reply means "no thanks" on both of those offers?
>>
>> The Mono 3.6 Releases Notes page was created about a week ago:
>>
>> http://www.mono-project.com/Release_Notes_Mono_3.6
>>
>> Xamarin.iOS-7.2.6 which was released about a week ago states "Mono
>> runtime/BCL updated to 3.6":
>>
>>
>> http://developer.xamarin.com/releases/ios/xamarin.ios_7/xamarin.ios_7.2/
>>
>> As of yesterday the Mono Project downloads page is showing Mono 3.6
>> links:
>>
>> http://www.go-mono.com/mono-downloads/download.html
>>
>> Damien notes ...
>>
>> They did not tag the HEAD of the branch, but an older commit!  But we
>> already had a set of RPMs based on that, so no rebuild was necessary.
>> I have updated MonoTizen's gh-pages to point to the matching
>> binaries:
>> 2d7113a..9f8394f  gh-pages -> gh-pages
>>
>> So can we consider Mono 3.6 to be released?Will there be a release
>> announcement today?
>>
>> I will update the http://monotizen.com page to include links to the
>> Tizen RPMs, and make my own announcement.
>>
>>
>> Cheers,
>> Bob Summerwill
>> Kitsilano Software
>>
>>
>> On Thu, Jul 31, 2014 at 9:34 AM, Bob Summerwill 
>> wrote:
>>
>>> 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"  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"  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 
> 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 

Re: [Mono-dev] Mono 3.6 release?

[Bob Summerwill]

It appears that the Forum system blackholed some e-mails from me.   Either
that, or they are still awaiting "moderator approval" a week later, so
let's try again ...


Jul 31, 2014; 9:30am [image: bobsummerwill][image: online]

 bobsummerwill


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


Jul 31, 2014; 9:34am [image: bobsummerwill][image: online]

 bobsummerwill


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 Wed, Aug 13, 2014 at 5:47 AM, Bob Summerwill  wrote:

> >> 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.
>
>
> I guess the non-reply means "no thanks" on both of those offers?
>
> The Mono 3.6 Releases Notes page was created about a week ago:
>
> http://www.mono-project.com/Release_Notes_Mono_3.6
>
> Xamarin.iOS-7.2.6 which was released about a week ago states "Mono
> runtime/BCL updated to 3.6":
>
>
> http://developer.xamarin.com/releases/ios/xamarin.ios_7/xamarin.ios_7.2/
>
> As of yesterday the Mono Project downloads page is showing Mono 3.6 links:
>
> http://www.go-mono.com/mono-downloads/download.html
>
> Damien notes ...
>
> They did not tag the HEAD of the branch, but an older commit!  But we
> already had a set of RPMs based on that, so no rebuild was necessary.
> I have updated MonoTizen's gh-pages to point to the matching binaries:
> 2d7113a..9f8394f  gh-pages -> gh-pages
>
> So can we consider Mono 3.6 to be released?Will there be a release
> announcement today?
>
> I will update the http://monotizen.com page to include links to the Tizen
> RPMs, and make my own announcement.
>
>
> Cheers,
> Bob Summerwill
> Kitsilano Software
>
>
> On Thu, Jul 31, 2014 at 9:34 AM, Bob Summerwill 
> wrote:
>
>> 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"  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"  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 
 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"  wrote:
>
>> Hello Bob,
>>
>> No, there is no public process for what we do.   But you can keep an
>> eye on the bugs going into Bugz

Re: [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.


I guess the non-reply means "no thanks" on both of those offers?

The Mono 3.6 Releases Notes page was created about a week ago:

http://www.mono-project.com/Release_Notes_Mono_3.6

Xamarin.iOS-7.2.6 which was released about a week ago states "Mono
runtime/BCL updated to 3.6":

http://developer.xamarin.com/releases/ios/xamarin.ios_7/xamarin.ios_7.2/

As of yesterday the Mono Project downloads page is showing Mono 3.6 links:

http://www.go-mono.com/mono-downloads/download.html

Damien notes ...

They did not tag the HEAD of the branch, but an older commit!  But we
already had a set of RPMs based on that, so no rebuild was necessary.
I have updated MonoTizen's gh-pages to point to the matching binaries:
2d7113a..9f8394f  gh-pages -> gh-pages

So can we consider Mono 3.6 to be released?Will there be a release
announcement today?

I will update the http://monotizen.com page to include links to the Tizen
RPMs, and make my own announcement.


Cheers,
Bob Summerwill
Kitsilano Software


On Thu, Jul 31, 2014 at 9:34 AM, Bob Summerwill  wrote:

> 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"  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"  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 
>>> 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"  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 
> 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.m...@clevertrove.com> wrote:
>>
>>> > From: mono-devel-list-boun...@lists.ximian.com [mailto:
>>> mono-devel-list-
>>> > boun...@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.
>>>
>>
>>
>>
>> --
>> b...@summerwill.net
>>
>>
>
>>>
>>> ___
>>> Mono-devel-list mailing list
>>> Mono-devel-list@lists.ximian.com
>>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>>
>>>


-- 
b...@summerwill.net
__