SVN tags here
https://svn.apache.org/repos/asf/incubator/devicemap/tags/devicemap

The name space is up to how we want to do this underneath each "component"
(hence the suggestion someone who can do this in JIRA might add actual
components for "Java", ".NET" or VB/CSharp and "Data", so far only Bertrand
and for some credentials like change assigneee Reza are in the right
group/role)

"data" had a snapshot for each OpenDDR update I synced. Reza missed 1.27,
but as we plan to draft a 1.0.0 milestone release, that can be done via the
release tag anyway.
So I'd do this for
https://svn.apache.org/repos/asf/incubator/devicemap/tags/data/1.0.0

Ideally all other tags should be similar. The naming convention is totally
different for every single Apache project.

For a "flat" structure using only the top-level "tags" folder, many
projects chose something like /tags/devicemap-data-1.0.0.

If you prefer, let's do that for ALL artifacts like that, otherwise just
"1.0.0" or "v1.0.0" are the other patterns. See "CouchDB" using a simple
"1.0.0", etc. "DeltaCloud" put a "release-" in front of every tag, so there
is no mandatory pattern by Apache Foundation, only a common agreement
inside each team it seems...

If we use the
/tags/data
/tags/devicemap

structure, then either
/tags/devicemap/java-1.0.0
/tags/devicemap/csharp-1.0.0
...
would work or
/tags/devicemap/java/1.0.0
/tags/devicemap/csharp/1.0.0

I'll leave the decision in the .NET and Java corner to what we like best.

I used "v1.x" under /data/openddr to match the exact same tag OpenDDR used
in Git.
No distinct preference here, but for /tags/data will do a simple 1.0.0 for
now.
As of now, "test-data" did not seem in the archive, and you did not sound
too eager to include it with a 1.0.0 release right now, is that correct?

Werner

On Wed, Jul 9, 2014 at 11:56 PM, eberhard speer jr. <[email protected]>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Ooops, lost me there "tagged" ?
>
> esjr
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.8 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJTvbqXAAoJEOxywXcFLKYctb4H/RJwOLzIjoFKcvRQIkN04uZC
> DjJGSayj8youkYwAMLY9AsM67osZfJkn0gCiXf+5Phpk5K9/PUJ5Qz8x3x5iizGe
> a/CQUXuVNyt/zRHXwc85lzuN+6FfC5uGsMGtbDFnf6Wm0ijBfEy3FZBAhHmdZFqB
> X774m9mI3URQWgqysoiip6UwZ64QKWdLth4KK0Ivyu02iMCwpQey5fWNgCIUvlp0
> c8SlkfvLy+n7xMEAQCjfgbh6E778tng7S2Ukurtowyfz83c/tyi/L/n+abEBEjMR
> F1OkW/SmJZZ3H9Skocq8G78PoCelWzd3JeAlJlmwTS10agF18kEAtJ9oEq67k3I=
> =e42w
> -----END PGP SIGNATURE-----
>

Reply via email to