You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devicemap.apache.org by Werner Keil <we...@gmail.com> on 2015/09/14 19:34:22 UTC
[VOTE] Release Apache DeviceMap C# client version 1.0.1
Hi,
I've prepared an official release of the Apache DeviceMap C# client
module 1.0.1.
Staging URL: https://people.apache.org/~wkeil/devicemap/
PNG files only for information purposes. I checked all signatures with
available tools either on the Linux instance or online, too.
Release tag:
https://svn.apache.org/repos/asf/devicemap/tags/releases/devicemap-csharp-client-1.0.1
JIRA issues addressed in this release:
https://issues.apache.org/jira/browse/DMAP/fixforversion/12333273/
Readme:
https://svn.apache.org/repos/asf/devicemap/trunk/clients/1.0/csharp/README
Please vote to approve this release:
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours.
If there's an urgent reply or concern, please don't forget to CC or BCC me
directly.
Otherwise we should see everybody's vote in the archive (for this month).
Thanks,
Werner
Re: [VOTE] Release Apache DeviceMap C# client version 1.0.1
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Mon, Sep 14, 2015 at 7:34 PM, Werner Keil <we...@gmail.com> wrote:
> ...Please vote to approve this release...
-1
devicemap-csharp-1.0.1-src.zip contains a binary log4net.dll which
should not be included in a source archive.
-Bertrand
Re: [VOTE] Release Apache DeviceMap C# client version 1.0.1
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, Sep 15, 2015 at 7:38 PM, Werner Keil <we...@gmail.com> wrote:
> ...Option 2 looks easier, not only because both archives would be smaller in
> size....
Removing logging in that module is not a problem for me.
-Bertrand
Re: [VOTE] Release Apache DeviceMap C# client version 1.0.1
Posted by Werner Keil <we...@gmail.com>.
Option 2 looks easier, not only because both archives would be smaller in
size.
If you strongly oppose, please let me know as soon as you can (also by CC).
Otherwise I would update the files and tryanother (hopefully last;-)
attempt in the course of this week.
Werner
On Tue, Sep 15, 2015 at 6:42 PM, Werner Keil <we...@gmail.com> wrote:
> Maybe harder for the Java-centric ones (I worked enough with .NET to understand and use both) to grasp, but I was under the impression devicemap-csharp-1.0.1-src.zip should allow a developer to instantly build the binary without extra hassle or involvement, right?
>
> Unlike Maven there is no proper build system for .NET that would dynamically pull a 3rd party DLL into the build process without having it in the local file system first.
>
> So please advice, what's best in your opinion:
>
> 1. Remove the DLL from the sources (not just the ZIP, if that reflects the codebase it also has to go from SVN) and modify the README so people know they have to fetch it from http://logging.apache.org/log4net/ and put it into a defined place before the project would build
>
> 2. Completely abandon logging here. Eberhard tried to use a Windows EventLog, but unless you run DeviceMap Console with Local Admin rights, that did not work and only result in secondary exceptions. Logging is only done for a few error situations anyway, so I could also remove the Log4Net dependendy and try to present error messages best they can in the console.
>
>
> WDYT?
>
>
> Please directly reply as CC or BCC with what you think is best, then I can modify the C# project.
>
>
> Thanks,
>
> Werner
>
>
> On Mon, Sep 14, 2015 at 7:34 PM, Werner Keil <we...@gmail.com> wrote:
> > ...Please vote to approve this release...
>
> -1
>
> devicemap-csharp-1.0.1-src.zip contains a binary log4net.dll which
> should not be included in a source archive.
>
> -Bertrand
>
>
Re: [VOTE] Release Apache DeviceMap C# client version 1.0.1
Posted by Werner Keil <we...@gmail.com>.
Maybe harder for the Java-centric ones (I worked enough with .NET to
understand and use both) to grasp, but I was under the impression
devicemap-csharp-1.0.1-src.zip should allow a developer to instantly
build the binary without extra hassle or involvement, right?
Unlike Maven there is no proper build system for .NET that would
dynamically pull a 3rd party DLL into the build process without having
it in the local file system first.
So please advice, what's best in your opinion:
1. Remove the DLL from the sources (not just the ZIP, if that reflects
the codebase it also has to go from SVN) and modify the README so
people know they have to fetch it from
http://logging.apache.org/log4net/ and put it into a defined place
before the project would build
2. Completely abandon logging here. Eberhard tried to use a Windows
EventLog, but unless you run DeviceMap Console with Local Admin
rights, that did not work and only result in secondary exceptions.
Logging is only done for a few error situations anyway, so I could
also remove the Log4Net dependendy and try to present error messages
best they can in the console.
WDYT?
Please directly reply as CC or BCC with what you think is best, then I
can modify the C# project.
Thanks,
Werner
On Mon, Sep 14, 2015 at 7:34 PM, Werner Keil <we...@gmail.com> wrote:
> ...Please vote to approve this release...
-1
devicemap-csharp-1.0.1-src.zip contains a binary log4net.dll which
should not be included in a source archive.
-Bertrand
Re: [VOTE] Release Apache DeviceMap C# client version 1.0.1
Posted by Werner Keil <we...@gmail.com>.
+1
Werner