Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (nike.apache.org: domain of eoglynn@gmail.com designates
 209.85.128.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=oZ9YX+5ZPSt4wjA/vxw2GUEbq5vreUUnGVBvXEM89Syrn60LVjnp+soWdiLvhktLox
         7klWAseXaFSdHwDbT5sfS4oxDPCH2ASaLdkMkig7KNHJ5X4dlWcjVkd/6AJ6+f/7Suhl
         wu/LO3nIRQy4WOeKU3/jfKcWR6KfQOdXTYsNc=
MIME-Version: 1.0
In-Reply-To: <200905051430.12236.dkulp@apache.org>
References: <cfdb37fb0905010939h68ed1969o1790cfd58e18c358@mail.gmail.com>
	 <200905041236.28869.dkulp@apache.org>
	 <a1e060230905050231qd52aafbif1a02c7cd04ce8bb@mail.gmail.com>
	 <200905051430.12236.dkulp@apache.org>
Date: Wed, 6 May 2009 14:10:18 +0100
Message-ID: <cfdb37fb0905060610k7d630120recdbf64bdfcd0350@mail.gmail.com>
Subject: Re: [VOTE] Release CXF dOSGi 1.0
From: Eoghan Glynn <eoglynn@gmail.com>
To: dev@cxf.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2009/5/5 Daniel Kulp <dkulp@apache.org>:
>
> OK.   That kind of make sense (along with what Eoghan said).
>
> However, I really think there needs to at least be a "README" in the
> distributions that describes a little what it is along with pointers to t=
he
> walkthroughs and such on the website.


I've added a README with an overview of the different distros and
pointers to getting started docco, mailing lists, JIRA etc:

http://svn.apache.org/viewvc/cxf/dosgi/trunk/distribution/multi-bundle/src/=
main/release/README?view=3Dmarkup

I've also addressed your other concerns in these two commits:

http://svn.apache.org/viewvc?rev=3D772157&view=3Drev
http://svn.apache.org/viewvc?rev=3D771670&view=3Drev

So I think we should be good to go with a second cut at this release.

Cheers,
Eoghan


2009/5/5 Daniel Kulp <dkulp@apache.org>:
>
> OK. =A0 That kind of make sense (along with what Eoghan said).
>
> However, I really think there needs to at least be a "README" in the
> distributions that describes a little what it is along with pointers to t=
he
> walkthroughs and such on the website.
>
> Right now, I download and unpack the the tarball and I look at it and say
> "uhh..... =A0what do I do with this?" =A0 =A0We definitely need a readme =
in there to
> describe things as well as provide pointers off to the web site, the user=
s@
> list for questions, etc.....
>
> Dan
>
>
>
> On Tue May 5 2009 5:31:49 am David Bosschaert wrote:
>> Hi Dan,
>>
>> On the samples, they are not part of the distribution because they can
>> be installed straight from the internet. All of the DOSGi
>> documentation is available here:
>> http://cxf.apache.org/distributed-osgi.html and which contains links
>> to the sample source code and a very detailed walkthrough of the
>> greeter sample:
>> http://cxf.apache.org/distributed-osgi-greeter-demo-walkthrough.html
>> As the OSGi containers install stuff straight from the internet, you
>> don't have to have the bundles available locally. Once the release is
>> out I'm planning to update this page to point straight to the sample
>> artefacts in maven.
>>
>> There is no such page for the spring-dm demo, I'll take an action to
>> provide such a page with the DOSGi documentation, but I don't think
>> this should hold up the release.
>>
>> Hope this makes sense to you,
>>
>> David
>>
>> 2009/5/4 Daniel Kulp <dkulp@apache.org>:
>> > I think I have to -1 this. =A0 Couple legal things need to get ironed =
out:
>> >
>> > 1) =A0Since this is a full "distribution" type thing, what parts of th=
at
>> > staging area will go into www.apache.org/dist/cxf? =A0 =A0 I ASSUME th=
e
>> > mutimodule bundle, but not really sure. =A0 =A0 Also, there needs to b=
e a
>> > tar.gz or zip of a "source" distribution of the whole contents of the
>> > tag. =A0 =A0That would also go into dist.
>> >
>> > 2) =A0I think some stuff in the NOTICE can be removed. =A0 For example=
: DOSGi
>> > doesn't ship the MTOSI stuff, that could be removed. =A0 Not major, bu=
t if
>> > a build has to be respun, let's get that cleaned up.
>> >
>> > 3) For the "distribution" builds, the LICENSE file needs to have at le=
ast
>> > the pointers to the LICENSES of the bundled deps appended to it. =A0 S=
ee
>> > the LICENSE in the cxf distributions. =A0 (remote-resources can do tha=
t, I
>> > may be able to help out tomorrow if I get out from under my backlog of
>> > email. =A0:-( =A0 )
>> >
>> > 4) Actually, IS there a distribution that includes the samples, possib=
le
>> > a readme, etc...? =A0 =A0 Should there be? =A0 Not a big deal either w=
ay, but a
>> > bit strange.
>> >
>> >
>> > Dan
>> >
>> > On Fri May 1 2009 12:39:48 pm Eoghan Glynn wrote:
>> >> Folks,
>> >>
>> >> I'm calling a vote to release CXF Distributed OSGi 1.0.
>> >>
>> >> The dOSGi subproject of CXF provides the Reference Implementation of
>> >> the Distribution Software (DSW) component of the Distributed OSGi
>> >> Specification[1].
>> >>
>> >> The staging area can be found at:
>> >>
>> >> =A0 http://people.apache.org/~eglynn/stage_cxf_dosgi
>> >>
>> >> This release is tagged with cxf-dosgi-ri-1.0 at:
>> >>
>> >> =A0 http://svn.apache.org/repos/asf/cxf/dosgi/tags/cxf-dosgi-ri-1.0
>> >>
>> >> The vote will remain open for at least 72 hours.
>> >>
>> >> Please consider this call to vote as my +1.
>> >>
>> >> Cheers,
>> >> Eoghan
>> >>
>> >> [1] See RFC 119 in
>> >> http://www.osgi.org/download/osgi-4.2-early-draft3.pdf
>> >
>> > --
>> > Daniel Kulp
>> > dkulp@apache.org
>> > http://www.dankulp.com/blog
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>