Re: What applications use SwingX?

Hi

Check the bugtracker under the username
"grandinj".  I even fixed some
table stuff for Jeanette just for fun.

> So why update at all? why not continue to use that
branch for the whole of that projects lifetime? By creating
your own copies you've just forced the continued maintenance
of all those components onto yourself. Seem to me that's far
harder than doing the odd set of code changes to bring
yourself up to the current swingx trunk every so often.
>
>   
Because all of the components have bugs. And if I upgrade to
the newer
release it also has bugs, just in a different place, thus
annoying my
clients no end, who are wanting their product to reach a
stable,
relatively bug-free state.
> Have you been using the vcs on a regular basis or only
used the 'official' milestone builds from the Swinglabs.org
site: 0.8, 0.9 etc.. unfortunately the milestones were
probably the wrong way to go in hindsight as they went 12
months (or more) 
I tried tracking the vcs, but see above why that doesn't
work.

What use are milestones unless you also do bug-fix releases
on those
milestones?

Look, I __know__ this is unpaid work for most people. I
appreciate it no
end, and I would love to become more involved.
I would be happy to be step in and maintain a "stable
branch". But what
chance do I have? This project appears to be managed by some
group of
people who are not even on this list, and who appear to do
releases for
marketing reasons.

But you can see why I'm struggling to commit my projects to
using SwingX?

Disclaimer: http://www.per
alex.com/disclaimer.html


------------------------------------------------------------
---------
To unsubscribe, e-mail: jdnc-unsubscribejdnc.dev.java.net
For additional commands, e-mail: jdnc-helpjdnc.dev.java.net

> Check the bugtracker under the username
"grandinj".  I even fixed some
> able stuff for Jeanette just for fun.

Yes you did contribute and thanks for that.
If this is about #88 I thought Richard explained it clearly
why this fix was not applied. There are other corner cases
which for which solution have to be found first.

> Because all of the components have bugs. And if I
upgrade to the newer
> release it also has bugs, just in a different place,
thus annoying my
> clients no end, who are wanting their product to reach
a stable,
> relatively bug-free state.

I could ask, how is this different from other software, but
instead I say this: It would be beneficial for both parties
(you as a user of the swingx library and us as developers)
if you have reported those issues back as soon as you have
found them. Having whatever changes we have made still fresh
on our minds would make easier to incorporate fixes for the
issues.

> What use are milestones unless you also do bug-fix
releases on those
> milestones?

What do you mean? We release milestone (or any other builds
for that matter) to provide fixes for issues reported
against previous builds. How is that different from bug
fixing milestones?

> I would be happy to be step in and maintain a
"stable branch". But what
> chance do I have? This project appears to be managed

Yet again, could you provide more details on what
"stable branch" means for you? Releases are
tagged, so can be the weekly builds so if you would want to
stay with any particular "release" you can (and
obviously you did from what you describe), however since
this is unpaid effort for most of the people we do not have
resources to apply any fixes twice (on head and on given
milestone). Further so even if we did it would still not
ensure that new bugs are not introduced on such a branch.
 
> by some group of people who are not even on this list,
and who appear
> to do releases for marketing reasons.

I did the last release and I'm not aware of any marketing
reason (hidden or obvious). Could you please enlighten me as
to what was on my mind when preparing that release? The only
reason I'm aware of was to provide back to community release
they were crying for for very long time.

I'm all open for constructive discussion and making this
project run more smoothly then it did in the past. I would
like to do more regular releases and get some reasonable
response times to new issues, But keep in mind that
resources we have are indeed limited and best thing to see
something done is to contribute yourself. I would understand
if you don't want or can not commit your time to
contributing patches for issue found, but even simple test
cases and issue reports are helpful and save time to those
who are going to fix it (Plus with a test case, you have a
chance to ensure problem doesn't recure in the future).

Regards,
Jan
[Message sent by forum member 'rah003' (rah003)]

http://forums.java.net/jive/thread.jspa?messageID=243910


------------------------------------------------------------
---------
To unsubscribe, e-mail: jdnc-unsubscribejdnc.dev.java.net
For additional commands, e-mail: jdnc-helpjdnc.dev.java.net