Hi, Sling does it on a top level as far as I saw, e.g.: http://svn.apache.org/viewvc/sling/tags/org.apache.sling.api-2.0.2-incubator/
Raising the interesting question, if we are also supposed to add the "-incubator" postfix to all of the currently released artifacts? If we use a dedicated "releases" subfolder for such "administrative" tags, leaving other folders to different tags, it sounds OK, e.g. it would leave a slightly cleaner tags folder than say Sling[?] Assuming all relevant artifacts under "java" or "csharp" are in such tag, then "devicemap-java-1.0.0" (with or without "-incubator" at the end, depending on whether we need it) sounds good. Otherwise, also see "org.apache.sling.discovery.standalone-1.0.0" vs. "org.apache.sling.discovery.support-1.0.0" adding the sub-component name like "qualifier", "client", "simpleddr" or whatever seems better. Sling does use OSGi like bundle names btw. something Bertrand tried to introduce earlier, but with many tags and archives frozen now, maybe we'd have to wait with that or consider, if exposing some (mostly Java) projects as OSGi bundles, too, could add value for users. Werner On Wed, Jul 16, 2014 at 9:51 AM, Bertrand Delacretaz <[email protected] > wrote: > Hi, > > I just created > http://svn.apache.org/repos/asf/incubator/devicemap/tags/releases/ > - it might be clearer to put all the tags for releases that we vote on > directly under there. with no subfolders? > > It's IMO fine to have other tags under /tags if needed, but it's good > for the ones that are about releases to be clearly identified. > > I would suggest using names like devicemap-java-1.0.0 for those tags, > that is the artifact name followed by version number. > > That's also similar to what we do in Sling, see [1]. That's a good > number of tags in the same folder, but even with Sling which does lots > of releases that's workable and clear. > > WDYT? > > -Bertrand > > [1] http://svn.apache.org/repos/asf/sling/tags/ >
