[prev in list] [next in list] [prev in thread] [next in thread]
List: log4net-dev
Subject: AW: Thoughts on 1.3
From: "Dominik Psenner" <dpsenner () gmail ! com>
Date: 2013-10-28 11:25:34
Message-ID: 004701ced3d0$75a06fb0$60e14f10$ () gmail ! com
[Download RAW message or body]
This is a multipart message in MIME format.
http://mail-archives.apache.org/mod_mbox/logging-log4net-dev/201310.mbox/%3C
CADVsjzOOzbBHOcKXRhqO-buGn5uEvurLy0WfykxqRMmtyPwvFw%40mail.gmail.com%3E
Von: Ramon Smits [mailto:ramon.smits@gmail.com]
Gesendet: Montag, 28. Oktober 2013 12:04
An: Log4NET Dev
Betreff: Re: Thoughts on 1.3
Why not just apply semver and make it v2?
-- Ramon
On Mon, Oct 28, 2013 at 8:36 AM, Dominik Psenner <dpsenner@gmail.com
<mailto:dpsenner@gmail.com> > wrote:
>On 2013-10-25, Dominik Psenner wrote:
>
>>> * the next release will be 1.3.0 and require .NET 2.0 or better
>
>>> I.e. we remove support for .NET 1.0 and 1.1, Compact Framework 1.0,
>>> Mono < 2.0, SSCLI and CLI 1.0 frameworks
>
>> That's even worth a +2! ;-)
>
>>> * the main assembly will get a new name like log4net-13.dll, only be
>>> signed by the new key
>
>>> * we provide two assemblies named log4net.dll signed with the old and
>>> new key respecitvely that contain type forwards to the new assembly
>>> only
>
>> I'm afraid that I can't quite grasp all the stuff we could break. We
should
>> definitely work out every possible usecase we may break. We have messed
>> enough and should try to not raise the tempers even more.
>
>Understood, I'll take that to the user list for a bigger audience -
>maybe people will see problems that we are overlooking.
Worth a try.
>>> stuff we haven't talked about, yet:
>
>>> * I'd like to split log4net-13.dll so that the main assembly can be used
>>> for the client profile and a separate assembly contains the stuff that
>>> requires System.Web - this way we no longer need the -cp builds.
>
>> The client profile was dropped with .NET 4.5 and previous versions are
>> automatically upgraded to include the missing DLLs once somebody runs an
>> update. Thus I'm not sure if we should really split the library and
double
>> the required efforts.
>
>I see. I wasn't aware the client profile was dropped again - spending
>most if not all of my working hours in Java land has made me lose track,
>or so it seems. In that case splitting the assembly doesn't make to
>much sense.
>
>And the client profile builds can be removed when log4net drops support
>for .NET 4.0 ten years from now ;-)
True. I wanted to quote where I have this information from:
http://msdn.microsoft.com/en-us/library/cc656912.aspx
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" \
CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 \
(filtered medium)"><style><!-- /* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.E-MailFormatvorlage18
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE link=blue vlink=purple><div \
class=WordSection1><p class=MsoNormal><span lang=EN-GB \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><a \
href="http://mail-archives.apache.org/mod_mbox/logging-log4net-dev/201310.mbox/%3CCADV \
sjzOOzbBHOcKXRhqO-buGn5uEvurLy0WfykxqRMmtyPwvFw%40mail.gmail.com%3E">http://mail-archi \
ves.apache.org/mod_mbox/logging-log4net-dev/201310.mbox/%3CCADVsjzOOzbBHOcKXRhqO-buGn5uEvurLy0WfykxqRMmtyPwvFw%40mail.gmail.com%3E</a></span><span \
lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-language:EN-US'><o:p></o:p></span></p><p \
class=MsoNormal><span lang=EN-GB \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-language:EN-US'><o:p> </o:p></span></p><div \
style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div \
style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p \
class=MsoNormal><b><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Von:</span></b><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> Ramon Smits \
[mailto:ramon.smits@gmail.com] <br><b>Gesendet:</b> Montag, 28. Oktober 2013 \
12:04<br><b>An:</b> Log4NET Dev<br><b>Betreff:</b> Re: Thoughts on \
1.3<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p \
class=MsoNormal>Why not just apply semver and make it v2?<o:p></o:p></p></div><div><p \
class=MsoNormal><br clear=all><o:p></o:p></p><div><div><p class=MsoNormal>-- \
Ramon<o:p></o:p></p></div></div><p class=MsoNormal \
style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Mon, Oct \
28, 2013 at 8:36 AM, Dominik Psenner <<a href="mailto:dpsenner@gmail.com" \
target="_blank">dpsenner@gmail.com</a>> wrote:<o:p></o:p></p><blockquote \
style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm \
6.0pt;margin-left:4.8pt;margin-right:0cm'><div><p class=MsoNormal \
style='margin-bottom:12.0pt'>>On 2013-10-25, Dominik Psenner \
wrote:<br>><br>>>> * the next release will be 1.3.0 and require .NET 2.0 \
or better<br>><br>>>> I.e. we remove support for .NET 1.0 and 1.1, \
Compact Framework 1.0,<br>>>> Mono < 2.0, SSCLI and CLI 1.0 \
frameworks<br>><br>>> That's even worth a +2! ;-)<br>><br>>>> * \
the main assembly will get a new name like log4net-13.dll, only be<br>>>> \
signed by the new key<br>><br>>>> * we provide two assemblies named \
log4net.dll signed with the old and<br>>>> new key respecitvely that \
contain type forwards to the new assembly<br>>>> \
only<br>><br>>> I'm afraid that I can't quite grasp all the stuff we \
could break. We<br>should<br>>> definitely work out every possible usecase we \
may break. We have messed<br>>> enough and should try to not raise the tempers \
even more.<br>><br>>Understood, I'll take that to the user list for a bigger \
audience -<br>>maybe people will see problems that we are \
overlooking.<o:p></o:p></p></div><p class=MsoNormal>Worth a \
try.<o:p></o:p></p><div><p class=MsoNormal \
style='margin-bottom:12.0pt'><br>>>> stuff we haven't talked about, \
yet:<br>><br>>>> * I'd like to split log4net-13.dll so that the main \
assembly can be used<br>>>> for the client profile and a separate \
assembly contains the stuff that<br>>>> requires System.Web - this way \
we no longer need the -cp builds.<br>><br>>> The client profile was dropped \
with .NET 4.5 and previous versions are<br>>> automatically upgraded to include \
the missing DLLs once somebody runs an<br>>> update. Thus I'm not sure if we \
should really split the library and<br>double<br>>> the required \
efforts.<br>><br>>I see. I wasn't aware the client profile was dropped \
again - spending<br>>most if not all of my working hours in Java land has made me \
lose track,<br>>or so it seems. In that case splitting the assembly doesn't \
make to<br>>much sense.<br>><br>>And the client profile builds can be \
removed when log4net drops support<br>>for .NET 4.0 ten years from now \
;-)<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>True. I \
wanted to quote where I have this information from:<br><br><a \
href="http://msdn.microsoft.com/en-us/library/cc656912.aspx" \
target="_blank">http://msdn.microsoft.com/en-us/library/cc656912.aspx</a><o:p></o:p></p></blockquote></div><p \
class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic