The simplest answer is to come up with something that is
not company-specific, so it doesn't get Apache into non-profit
legal trouble, yet addresses these real needs. How about
a basic "monthly stabilization branch" that anyone can pull
off of, and has no particular tie to any one company? And
a long-term strategy of eliminating the need for such branches
once we have a real set of releases?
What would others say to something basic like that?
I like the idea of "monthly stabilization branch". I think that also
helps this community. It can use these branches for building their
apps against it, instead of against a trunk. I mean from this point
there is really no tie to a company. Oracle is a user like other
companies (see [1]).
This approach *may* (not must!) look to much like a *real* Apache
product. One statement I read on [EMAIL PROTECTED] about having maven
repos for Incubator is the following:
<snip>
...
It is not the goal of the Apache software foundation to have Incubator
code *too* widely available. The Incubator is a firewall between ASF
and Incubator code ... And if people don't start respecting that, we
may find that the voices asking to push the Incubator to an entirely
separate domain win out, which I would consider a bad thing.
...
Remember: we're not trying to make Incubator code *too* widely available.
Only very committed users should be touching it at all.
...
</snip>
I understand that point and I'd also like to see Trinidad becoming
more and more stable. Why not monthly?
I am not really sure how that violates against the quoted sniplet. Our
users are very committed users. I'd speak more of developers. We
already had several patches and enhancements by this community. From
my personal point of view it doesn't violate. The incubation is all
about the development community. So why not going forward and
providing these monthly branches?
-Matthias
[1] http://wiki.apache.org/myfaces/Companies_using_Trinidad
-- Adam
>
> I'm also going to do some thinking about this with regard to Shale (again,
> need to get to a stable release first, but that shouldn't be an infinite
> amount of time any more :-).
>
> -- Adam
> >
> >
> Craig
>
>
> Craig
> >
> >
>
>
--
Matthias Wessendorf
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
