cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Debbie Moynihan" <debbiemoyni...@gmail.com>
Subject Re: Celtix and Xfire future support and maintenance
Date Fri, 01 Sep 2006 20:31:19 GMT
Just to be clear would it be acceptable for the  maintenance releases of
Celtix to be developed and made available at ObjectWeb rather than Apache -
assuming we make it clear that the project is being discontinued on the
project site at ObjectWeb?

On 9/1/06, Jim Jagielski <jim@jagunet.com> wrote:
>
> It's expected, I think, that the separate releases of Celtix and XFire
> will be reduced to maint. only at present, but to make it clear
> that the projects are being discontinued.
>
> On Sep 1, 2006, at 10:39 AM, Dan Diephouse wrote:
>
> > Why not just continue using ObjectWeb for the 1.x release of
> > Celtix? You're going to have a much harder time trying to do
> > releases here as you'll need to get all the licensing requirements
> > met and it will probably end up being a distraction from the
> > project. This is what XFire is doing. Additionally I don't really
> > see what in the proposal you're referring to. The proposal was for
> > the XFire/Celtix merge. I think we'll run into issues in the
> > incubator if we did a release of just XFire or just Celtix. I
> > believe we even told them on the incubator list that we'd keep
> > doing maintenance releases at their original homes.
> >
> > - Dan
> >
> > Bozhong Lin wrote:
> >
> >> Hi,
> >>
> >> One topic discussed during CeltiXfire proposal is about Celtix and
> >> Xfire maintenance after they are merged and move to Apache
> >> community. Currently, we are considering to do further Celtix bug
> >> fixes and maintenance releases out of Apache community, thus to
> >> help existing Celtix users gradually adapt to Apache community. In
> >> order to do so, we have a couple issues to be resolved:
> >> 1. A branch for Celtix latest code in Objectweb. Right now, there
> >> is a tag for latest code from Objectweb, we need to create a
> >> branch for this tag, thus allowing bug fixes for Celtix to be
> >> committed into this branch.
> >> 2. Publishing snapshots for Celtix maintenance releases. We
> >> obviously need ability to publish Celtix snapshots if we are going
> >> to do maintenance out of Apache community. What is Apache policy
> >> related to publish snapshots under this situation.
> >>
> >> Thanks,
> >> Bo
> >
> >
> >
> > --
> > Dan Diephouse
> > (616) 971-2053
> > Envoi Solutions LLC
> > http://netzooid.com
> >
>
>

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