You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Guillaume Nodet <gn...@gmail.com> on 2009/09/29 14:51:22 UTC
SVN tree and Git mirror available
I've set up the default structure for the svn tree so that we can have
a git mirror for those that are interested in using this.
The svn repo is available at:
https://svn.apache.org/repos/asf/incubator/aries/trunk
For git, the git clone url is available at
git://git.apache.org/aries.git
More informations on Git from http://git.apache.org/ and especially
http://wiki.apache.org/general/GitAtApache
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: SVN tree and Git mirror available
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
IIUC, these will cherry pick products out of the source tree. I
strongly dislike this style of organization.
On Sep 29, 2009, at 11:12 AM, Guillaume Nodet wrote:
> I've no idea yet ;-)
> Having a single trunk does not necesseraly mean we release
> everything together.
> Felix works this way and maven plugins too (or at least they used to).
>
> 2009/9/29 Alan D. Cabrera <li...@toolazydogs.com>:
>>
>> On Sep 29, 2009, at 5:51 AM, Guillaume Nodet wrote:
>>
>>> I've set up the default structure for the svn tree so that we can
>>> have
>>> a git mirror for those that are interested in using this.
>>>
>>> The svn repo is available at:
>>> https://svn.apache.org/repos/asf/incubator/aries/trunk
>>
>>
>> Are we going to release blueprint in tandem with the rest of the
>> Aries products?
>>
>>
>> Regards,
>> Alan
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
Re: SVN tree and Git mirror available
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Tue, Sep 29, 2009 at 10:51 PM, Jeremy Hughes <hu...@apache.org> wrote:
> 2009/9/29 Guillaume Nodet <gn...@gmail.com>:
>>.. Having a single trunk does not necesseraly mean we release everything together.
>> Felix works this way and maven plugins too (or at least they used to).
>
> How does this work w.r.t subproject interdependencies ... how does a
> user know what levels of the subprojects have been tested with each
> other are are known to work together. e.g. foo@1.1 depends on has been
> tested with bar@1.2 ... a new bar@1.3 is released but how do users
> know whether they're ok using foo@1.1 with bar@1.3 ?...
In Sling [1], the way we handle this is with integration tests. The
tests in svn (Sling's launchpad/testing module) use a set combination
of bundles, but you can easily run them against any other combination.
We do "big bang" releases from time to time, and release individual
bundles in between, or rather groups of bundles.
-Bertrand
[1] http://sling.apache.org
Re: SVN tree and Git mirror available
Posted by Guillaume Nodet <gn...@gmail.com>.
On Tuesday, September 29, 2009, Jeremy Hughes <hu...@apache.org> wrote:
> 2009/9/29 Guillaume Nodet <gn...@gmail.com>:
>> I've no idea yet ;-)
>> Having a single trunk does not necesseraly mean we release everything together.
>> Felix works this way and maven plugins too (or at least they used to).
>
> How does this work w.r.t subproject interdependencies ... how does a
> user know what levels of the subprojects have been tested with each
> other are are known to work together. e.g. foo@1.1 depends on has been
> tested with bar@1.2 ... a new bar@1.3 is released but how do users
> know whether they're ok using foo@1.1 with bar@1.3 ? The combinations
> can get mind-boggling. Perhaps it just works!?!? I don't know Felix
> well enough to say.
We have the maven dependecies plus the osgi package versioning and
constraints to deal with those problems, so I don't think the argument
holds.
> Initially I would prefer to release all of what we have together so
> there is no confusion with users. As the project grow we can revisit.
I think it's quite difficult to balance anything related to the
release cycle right now, and we should wait a bit until more code
comes in and see how to organize it. But given the blueprint
implementation is already consumed by other Apache projects (mostly
Felix Karaf for now afaik), it might make sense to keep separate
release cycle to be able to release new features or bug fixes more
easily.
Having more fined grained releases makes it easier to keep up with the
"release early, release often" mantra.
In Felix, it seems to work quite well. Of course, the drawback is
that there are often releases to review and vote on, but it does seem
a big problem.
So, in conclusion, if components are highly tied together, it makes
sense to release them together: for example transactions support for
blueprint should imho be released along with the blueprint core
implementation. But an RFC 66 implementation and blueprint do not
have to be released together.
But I think the svn organization question can be somewhat separated
from the release cycle of the different components, and the maven
release plugin can deal with a single trunk without any problems.
>>
>> 2009/9/29 Alan D. Cabrera <li...@toolazydogs.com>:
>>>
>>> On Sep 29, 2009, at 5:51 AM, Guillaume Nodet wrote:
>>>
>>>> I've set up the default structure for the svn tree so that we can have
>>>> a git mirror for those that are interested in using this.
>>>>
>>>> The svn repo is available at:
>>>> https://svn.apache.org/repos/asf/incubator/aries/trunk
>>>
>>>
>>> Are we going to release blueprint in tandem with the rest of the Aries products?
>>>
>>>
>>> Regards,
>>> Alan
>>>
>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>
Re: SVN tree and Git mirror available
Posted by Jeremy Hughes <hu...@apache.org>.
2009/9/29 Guillaume Nodet <gn...@gmail.com>:
> I've no idea yet ;-)
> Having a single trunk does not necesseraly mean we release everything together.
> Felix works this way and maven plugins too (or at least they used to).
How does this work w.r.t subproject interdependencies ... how does a
user know what levels of the subprojects have been tested with each
other are are known to work together. e.g. foo@1.1 depends on has been
tested with bar@1.2 ... a new bar@1.3 is released but how do users
know whether they're ok using foo@1.1 with bar@1.3 ? The combinations
can get mind-boggling. Perhaps it just works!?!? I don't know Felix
well enough to say.
Initially I would prefer to release all of what we have together so
there is no confusion with users. As the project grow we can revisit.
>
> 2009/9/29 Alan D. Cabrera <li...@toolazydogs.com>:
>>
>> On Sep 29, 2009, at 5:51 AM, Guillaume Nodet wrote:
>>
>>> I've set up the default structure for the svn tree so that we can have
>>> a git mirror for those that are interested in using this.
>>>
>>> The svn repo is available at:
>>> https://svn.apache.org/repos/asf/incubator/aries/trunk
>>
>>
>> Are we going to release blueprint in tandem with the rest of the Aries products?
>>
>>
>> Regards,
>> Alan
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
Re: SVN tree and Git mirror available
Posted by Guillaume Nodet <gn...@gmail.com>.
I've no idea yet ;-)
Having a single trunk does not necesseraly mean we release everything together.
Felix works this way and maven plugins too (or at least they used to).
2009/9/29 Alan D. Cabrera <li...@toolazydogs.com>:
>
> On Sep 29, 2009, at 5:51 AM, Guillaume Nodet wrote:
>
>> I've set up the default structure for the svn tree so that we can have
>> a git mirror for those that are interested in using this.
>>
>> The svn repo is available at:
>> https://svn.apache.org/repos/asf/incubator/aries/trunk
>
>
> Are we going to release blueprint in tandem with the rest of the Aries products?
>
>
> Regards,
> Alan
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: SVN tree and Git mirror available
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
On Sep 29, 2009, at 5:51 AM, Guillaume Nodet wrote:
> I've set up the default structure for the svn tree so that we can have
> a git mirror for those that are interested in using this.
>
> The svn repo is available at:
> https://svn.apache.org/repos/asf/incubator/aries/trunk
Are we going to release blueprint in tandem with the rest of the Aries
products?
Regards,
Alan