ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Koelewijn <denis.koelew...@gmail.com>
Subject Re: [VOTE] Graduate ACE from the Apache Incubator
Date Thu, 17 Nov 2011 14:57:58 GMT
The svn directory tags/ is there to place 'tags' (duh ;-) on specific
revisions in the repository. These tags can be anything, including the
identification of a release, release candidates, or specific bug-fixes.
IMHO the de-facto way of working with svn is to use tags/ for all these
kind naming of revision. It is completely possible to do it differently,
with the (small) penalty that this devition from the norm needs to
explained over and over, because people are used to the de-facto way of
working.

Regards,

Denis

On Thu, Nov 17, 2011 at 15:49, Karl Pauls <karlpauls@gmail.com> wrote:

> and is what felix has been doing all along as we didn't like the term
> tags for releases :-)
>
> regards,
>
> Karl
>
> On Thu, Nov 17, 2011 at 3:47 PM, Guillaume Nodet <gnodet@gmail.com> wrote:
> > Yeah, the fact that the tree containing the tags is named "releases"
> > instead of "tags" just does not follow svn usual practices, but that's
> not
> > a problem in itself.
> >
> > On Thu, Nov 17, 2011 at 15:45, Karl Pauls <karlpauls@gmail.com> wrote:
> >
> >> Not sure what you are talking about. We do have takes for the
> >> artifacts in svn. They are in the releases dir. We just don't have a
> >> tag for the trunk at that point but only for the individual
> >> subprojects just like felix is doing it as well (and sling iirc).
> >>
> >> http://svn.apache.org/repos/asf/incubator/ace/releases/
> >>
> >> regards,
> >>
> >> Karl
> >>
> >> On Thu, Nov 17, 2011 at 3:39 PM, Bertrand Delacretaz
> >> <bdelacretaz@apache.org> wrote:
> >> > (moving thread here from general@incubator.a.o)
> >> >
> >> > On Thu, Nov 17, 2011 at 3:07 PM, Karl Pauls <karlpauls@gmail.com>
> wrote:
> >> >> $ mkdir org.apache.ace.client.automation-0.8.0-incubator
> >> >> $ cd org.apache.ace.client.automation-0.8.0-incubator/
> >> >> $ wget
> >>
> http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator-source.jar
> >> >> $ jar -xf
> org.apache.ace.client.automation-0.8.0-incubator-sources.jar
> >> >> $ wget
> >>
> http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator.pom
> >> >> $ mv org.apache.ace.client.automation-0.8.0-incubator.pom pom.xml
> >> >> $ mvn clean install
> >> >
> >> > I agree with others that having an svn tag for that release would be
> >> > much more convenient, and it's the expected way. IIRC you're only
> >> > expected to keep the latest release under /dist, so the above URLs
> >> > will change over time, and it's too easy to delete those files by
> >> > mistake.
> >> >
> >> > What prevents you from creating svn tags when releasing bundles?
> >> >
> >> > Sling does release bundles individually, and we do have svn tags under
> >> > http://svn.apache.org/repos/asf/sling/tags/
> >> >
> >> > -Bertrand
> >> >
> >>
> >>
> >>
> >> --
> >> Karl Pauls
> >> karlpauls@gmail.com
> >> http://twitter.com/karlpauls
> >> http://www.linkedin.com/in/karlpauls
> >> https://profiles.google.com/karlpauls
> >>
> >
> >
> >
> > --
> > ------------------------
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> > ------------------------
> > Open Source SOA
> > http://fusesource.com
> >
>
>
>
> --
> Karl Pauls
> karlpauls@gmail.com
> http://twitter.com/karlpauls
> http://www.linkedin.com/in/karlpauls
> https://profiles.google.com/karlpauls
>

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