Yes, a jsf-comp release has more advantages if you compare it with a sandbox release. The disadvantage is that I can no longer impress people by saying that I have a component in myfaces for now:)

Let me make a release at jsf-comp, then we will see what happens. By the way the library donation is currently in patch available state at jira, is it going to be canceled for now?

Regards,

Cagatay

On 4/17/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
On 4/17/06, Cagatay Civici <[EMAIL PROTECTED]> wrote:
> Well Mike, I have some new features and enhancements in my mind. Adding
> these features making a release at jsf-comp, receive feedback and
> stabilizing them seems a good idea at first glance.
>
> The other way around should be that the library is committed to sandbox and
> I provide patches. I favor the first way since I am a commiter at jsf-comp
> and people planning to use the library need to build sandbox from source by
> themselves.
>
> I'm confused a bit now, maybe you should decide both ways are fine for me in
> the end.

I think it's perfectly fine if you release them from jsf-comp, from
the sandbox, or both.   :)

Since there's some question about how these will fit in with ADF Faces
and since you're planning on more changes, you might find jsf-comp a
good place to start if you don't mind the extra work of releasing them
yourself.

Whether or not they are available at jsf-comp should have no bearing
on whether we commit them to the sandbox, but increasing the user-base
and quality of the code probably will encourage us to act more quickly
:)

As you point out, currently end-users have to do a checkout and
manually build the sandbox, so that limits who'd be able to use the
component if it's not in a usable sandbox state during a Tomahawk
release.

Reply via email to