Re: [Mono-dev] [Fwd: Planning for Mono 1.2: API freeze.]
Ok, I just thought that as it could impose some changes internally on mod_mono and also on mod_mono building on Win32, there could be some hurry on commiting it before API Freeze ... Thanks again ... Em Seg, 2006-01-02 às 14:06 -0500, Miguel de Icaza escreveu: Hello, > Would the mod_mono Win32 patch be in or out this 1.2 release? Support for Win32 is not an API change, hence it will eventually be integrated. > If it is desired, how should I proceed? Wait for gonzalo or talk > directly to you? Wait for Gonzalo as I said before. Miguel ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list -- Regards, Alexandre Rocha Lima e Marcondes P4 Tecnologia e Desenvolvimento Humano [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] www.p4tecnologia.com alexandre.p4tecnologia.com Projetos: MonoBrasil MonoBASIC ACBr Freedom ERP To validate this message's signature follow the instructions: http://www.cacert.org/index.php?id=3&lang=en_US smime.p7s Description: S/MIME cryptographic signature ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
RE: [Mono-dev] [Fwd: Planning for Mono 1.2: API freeze.]
Hi Miguel, > You can still use the NUnit as provided by the NUnit maintainers, they > should distribute it in Unix-installable form and distribute a > pkg-config .pc file, which would allow folks to use the new NUnit. > > Miguel Great idea! Somebody volunteer please. :-) Charlie ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Fwd: Planning for Mono 1.2: API freeze.]
Dnia 02-01-2006, pon o godzinie 12:55 -0500, Miguel de Icaza napisał(a): > Załącznik: wiadomość e-mail, "Forwarded message - Planning for Mono > 1.2: API freeze." > > Przesyłany list -- > > Od: Miguel de Icaza <[EMAIL PROTECTED]> > > Dla: Mono Hackers <[EMAIL PROTECTED]> > > Temat: Planning for Mono 1.2: API freeze. > > Data: Mon, 02 Jan 2006 12:54:19 -0500 > > > > Hello folks, > > > > I know that this is a very short notice, I should have mentioned > > this in mid-December, but I completely blanked out. > > > > We are going to API freeze Mono this week. If you have any API > > changes that you want to make, please contact me directly. > > > > What this means is that the public API of the Mono-specific > > libraries will cease to change, although we can continue to bug fix it > > and document it. > > > > The .NET libraries already had their APIs set in stone, so those > > will continue to be developed (implementing NotImplementedExceptions, > > fixing bugs and implementing NET_2_0 protected code). > > > > Changes to the .NET public API to fix differences against the > > published .NET interface is ok (specially in the 2.x universe, as Mono > > 1.2 will not guarantee .NET 2.0 support in full anyways, so things are > > much more lax there). > > > > So in short: you can change implementation bits, but not public > > interfaces. > > > > If an API change is /absolutely required/ this needs to be discussed > > before the patch makes it into SVN. API from NET 2.0 (Microsoft.Build.*) isn't considered stable? Code that is currently in SVN was obsoleted by new NET 2.0 release and it needs some changes. There is absolutely no compatibility between these two versions (from Beta 2 and 2.0). I added some code to new Mono.XBuild namespaces. I think that something of it can also change to make it work with 2.0 Microsoft.Build. -- Marek Sieradzki <[EMAIL PROTECTED]> ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Fwd: Planning for Mono 1.2: API freeze.]
Hello, > Would the mod_mono Win32 patch be in or out this 1.2 release? Support for Win32 is not an API change, hence it will eventually be integrated. > If it is desired, how should I proceed? Wait for gonzalo or talk > directly to you? Wait for Gonzalo as I said before. Miguel ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Fwd: Planning for Mono 1.2: API freeze.]
Hey, > Well, actually the patch in mentioned bug is exactly the needed "build > system change". Everything to do here is to apply it. Upgrading NUnit > itself in mono tree is not needed, we just need to tweak the place > where config files are installed. Ah, that sounds fine. I thought this was the discussion about upgrading the NUnit we ship. We should review the patch, but it is not an API changing change, so there is no rush. > > > > > You can still use the NUnit as provided by the NUnit maintainers, they > > should distribute it in Unix-installable form and distribute a > > pkg-config .pc file, which would allow folks to use the new NUnit. > > Yap, that is right. I can also use the patch included in bug (one of > the reasons I created it was to allow use of nunit-console2 to all the > people using mono). > > If it is really too late for this patch to get into the tree, then I'm > fine with this. You just asked for pending changes, and here is one. > > -- > Kamil Skalski > http://nazgul.omega.pl > -- Miguel de Icaza <[EMAIL PROTECTED]> Novell, Inc. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Fwd: Planning for Mono 1.2: API freeze.]
Hello Miguel, Would the mod_mono Win32 patch be in or out this 1.2 release? If it is desired, how should I proceed? Wait for gonzalo or talk directly to you? Em Seg, 2006-01-02 às 12:55 -0500, Miguel de Icaza escreveu: anexo Mensagem de correio, "Forwarded message - Planning for Mono 1.2: API freeze." Mensagem encaminhada De: Miguel de Icaza <[EMAIL PROTECTED]> Para: Mono Hackers <[EMAIL PROTECTED]> Assunto: Planning for Mono 1.2: API freeze. Data: Mon, 02 Jan 2006 12:54:19 -0500 Programa de correio: Evolution 2.4.0 Hello folks, I know that this is a very short notice, I should have mentioned this in mid-December, but I completely blanked out. We are going to API freeze Mono this week. If you have any API changes that you want to make, please contact me directly. What this means is that the public API of the Mono-specific libraries will cease to change, although we can continue to bug fix it and document it. The .NET libraries already had their APIs set in stone, so those will continue to be developed (implementing NotImplementedExceptions, fixing bugs and implementing NET_2_0 protected code). Changes to the .NET public API to fix differences against the published .NET interface is ok (specially in the 2.x universe, as Mono 1.2 will not guarantee .NET 2.0 support in full anyways, so things are much more lax there). So in short: you can change implementation bits, but not public interfaces. If an API change is /absolutely required/ this needs to be discussed before the patch makes it into SVN. Miguel ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list -- Regards, Alexandre Rocha Lima e Marcondes P4 Tecnologia e Desenvolvimento Humano [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] www.p4tecnologia.com alexandre.p4tecnologia.com Projetos: MonoBrasil MonoBASIC ACBr Freedom ERP To validate this message's signature follow the instructions: http://www.cacert.org/index.php?id=3&lang=en_US smime.p7s Description: S/MIME cryptographic signature ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Fwd: Planning for Mono 1.2: API freeze.]
> > We wont be able to upgrade NUnit on time. > > Upgrading NUnit in our tree will likely require build system changes and > there is no time to include those. Well, actually the patch in mentioned bug is exactly the needed "build system change". Everything to do here is to apply it. Upgrading NUnit itself in mono tree is not needed, we just need to tweak the place where config files are installed. > > You can still use the NUnit as provided by the NUnit maintainers, they > should distribute it in Unix-installable form and distribute a > pkg-config .pc file, which would allow folks to use the new NUnit. Yap, that is right. I can also use the patch included in bug (one of the reasons I created it was to allow use of nunit-console2 to all the people using mono). If it is really too late for this patch to get into the tree, then I'm fine with this. You just asked for pending changes, and here is one. -- Kamil Skalski http://nazgul.omega.pl ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Fwd: Planning for Mono 1.2: API freeze.]
Hello, > There is still a pending patch for > http://bugzilla.ximian.com/show_bug.cgi?id=76928 > > I'm not sure if this could be called a "mono specific public API", but > in some way a script name is such an API ;-) We wont be able to upgrade NUnit on time. Upgrading NUnit in our tree will likely require build system changes and there is no time to include those. You can still use the NUnit as provided by the NUnit maintainers, they should distribute it in Unix-installable form and distribute a pkg-config .pc file, which would allow folks to use the new NUnit. Miguel ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Fwd: Planning for Mono 1.2: API freeze.]
There is still a pending patch for http://bugzilla.ximian.com/show_bug.cgi?id=76928 I'm not sure if this could be called a "mono specific public API", but in some way a script name is such an API ;-) 2006/1/2, Miguel de Icaza <[EMAIL PROTECTED]>: > > -- > Miguel de Icaza <[EMAIL PROTECTED]> > Novell, Inc. > > > > -- Wiadomość oryginalna -- > From: Miguel de Icaza <[EMAIL PROTECTED]> > To: Mono Hackers <[EMAIL PROTECTED]> > Date: Mon, 02 Jan 2006 12:54:19 -0500 > Subject: Planning for Mono 1.2: API freeze. > Hello folks, > > I know that this is a very short notice, I should have mentioned > this in mid-December, but I completely blanked out. > > We are going to API freeze Mono this week. If you have any API > changes that you want to make, please contact me directly. > > What this means is that the public API of the Mono-specific > libraries will cease to change, although we can continue to bug fix it > and document it. > > The .NET libraries already had their APIs set in stone, so those > will continue to be developed (implementing NotImplementedExceptions, > fixing bugs and implementing NET_2_0 protected code). > > Changes to the .NET public API to fix differences against the > published .NET interface is ok (specially in the 2.x universe, as Mono > 1.2 will not guarantee .NET 2.0 support in full anyways, so things are > much more lax there). > > So in short: you can change implementation bits, but not public > interfaces. > > If an API change is /absolutely required/ this needs to be discussed > before the patch makes it into SVN. > > Miguel > > > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > > -- Kamil Skalski http://nazgul.omega.pl ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] [Fwd: Planning for Mono 1.2: API freeze.]
-- Miguel de Icaza <[EMAIL PROTECTED]> Novell, Inc. --- Begin Message --- Hello folks, I know that this is a very short notice, I should have mentioned this in mid-December, but I completely blanked out. We are going to API freeze Mono this week. If you have any API changes that you want to make, please contact me directly. What this means is that the public API of the Mono-specific libraries will cease to change, although we can continue to bug fix it and document it. The .NET libraries already had their APIs set in stone, so those will continue to be developed (implementing NotImplementedExceptions, fixing bugs and implementing NET_2_0 protected code). Changes to the .NET public API to fix differences against the published .NET interface is ok (specially in the 2.x universe, as Mono 1.2 will not guarantee .NET 2.0 support in full anyways, so things are much more lax there). So in short: you can change implementation bits, but not public interfaces. If an API change is /absolutely required/ this needs to be discussed before the patch makes it into SVN. Miguel --- End Message --- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
