devicemap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Werner Keil <werner.k...@gmail.com>
Subject Re: [PROPOSE] Release DeviceMap-data and other dependencies (with connection URL etc. fixed)
Date Wed, 07 Sep 2016 15:02:34 GMT
Then why can Karaf publish something DeviceMap can't ?

Is their "tutorial/latest" simply part of the "site" which does not fall
under the release constraints?

Again, as all the clients stand, especially the .NET ones (but without
significant improvement to add a "Remote JAR" option, also the Java Client)
a ZIP or JAR file on a remote server is worthless to all DeviceMap clients.

If it's not possible to make the "data" folder and URL available in a
proper way (http://devicemap.apache.org/ will likely continue to exist,
only with the "retired" warning if it gets archived, so
http://devicemap.apache.org/data hypothetically also would, but nobody is
even able to start or maintain the VM after the PMC stops) then I don't
think any further release is worth the effort.

Werner

Hi,

On Wed, Sep 7, 2016 at 1:42 PM, Werner Keil <werner.keil@gmail.com> wrote:
> ...Can we turn
> http://devicemap-vm.apache.org/data/latest/
> into
> http://devicemap.apache.org/data/latest/ ...

No, because that data must be published via the Apache release process
as per http://www.apache.org/dev/release-publishing and then
distributed at least
viahttps://dist.apache.org/repos/dist/release/devicemap/ and possibly
other common channels.

Once again, for this to happen you just need to create an archive of
what needs to be released, sign it and make it available so that this
PMC can vote on it - while it still exists.

-Bertrand

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message