Mono-3.6.0 RPMs for Tizen released.Mono for Sailfish is next.
http://kitsilanosoftware.wordpress.com/2014/08/15/mono-3-6-0-rpms-for-tizen-released/
Cheers,
Bob
On Wed, Aug 13, 2014 at 11:09 AM, Bob Summerwill b...@summerwill.net wrote:
OK - I'll proceed with my own announcement.
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
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]
FYI, these came through just fine.
On Wed, Aug 13, 2014 at 9:24 AM, Bob Summerwill b...@summerwill.net 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;
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
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
Hokey dokey - thanks for the confirmation.
On Wed, Aug 13, 2014 at 9:34 AM, Miguel de Icaza mig...@xamarin.com 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.
OK - I'll proceed with my own announcement.
Cheers,
Bob
On Wed, Aug 13, 2014 at 9:35 AM, Jo Shields direct...@apebox.org 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
And as for Abode ... they are real losers, aren't they? They are so
unloved and being chopped apart at the seams.
Adobe Reader and Flash are certainly some of the most irritating pieces of
software I have on my machines, and I will be delighted to be finally rid
of both of them in the not too
On 07/30/2014 05: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.
Bob,
Adding Tizen RPMs to
Ha ha!Happy exploration, Jo. Good to meet you!
Cheers,
Bob
On Thu, Jul 31, 2014 at 5:11 AM, Jo Shields direct...@apebox.org wrote:
On 07/30/2014 05:41 PM, Bob Summerwill wrote:
That's what I thought, Miguel.
Thanks for the clarification.
With regard to the Tizen RPMs, should I
The Tizen RPMs for Mono-3.6 are hosted on the Github Page for MonoTizen,
which is ...
https://github.com/kitsilanosoftware/MonoTizen/tree/gh-pages/rpms
Which then maps to ...
http://kitsilanosoftware.github.io/MonoTizen/
These are the main RPMs for the production Tizen-2.2.1 release:
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
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
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,
PS. Ditto for the MonoDevelop.Tizen add-in and for the Tizen SDK bindings
when we have those working.
MonoTizen is not a fork or product. It's just a manner to get Mono for
Tizen working.
I'm also working on getting Mono directly into the Tizen distro itself, as
has already happened for Qt, as
On 29/07/2014 22:59, Miguel de Icaza wrote:
Yes, we do make a branch, and then we put it through QA.
The we fix all the bugs that QA finds, and when we are ready we release.
What is important is to not regress, so things will take as long as
they need to, because we are not going to ship a
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
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
On 30/07/2014 16:00, 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
On 30/07/2014 16:00, 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
We are not fast or rushed either however we need to run a massive number of
regressions against mono and it would be good to be able to do this
concurrently with the mono QA both for us and for mono :)
On Wed, Jul 30, 2014 at 6:00 PM, Bob Summerwill b...@summerwill.net wrote:
I'm not in a
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 b...@summerwill.net wrote:
I'm not in a rush. I'm just trying to
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 mig...@xamarin.com
What is the plan for the Mono 3.6 release?Who is the Release Manager?
Rodrigo? What is the process?
Some more transparency to the community around Mono release process would
be helpful. Thanks!
+!
On Wed, Jul 30, 2014 at 12:16 AM, Bob Summerwill b...@summerwill.net wrote:
Hey guys,
Yes, we do make a branch, and then we put it through QA.
The we fix all the bugs that QA finds, and when we are ready we release.
What is important is to not regress, so things will take as long as they
need to, because we are not going to ship a version that breaks someone's
system, just
26 matches
Mail list logo
