Releasing 0.6
by Randall Hauch
During the 0.6 release cycle, we've added a few new features and fixed
quite a few issues with the graph library, connectors, and JCR
implementation [1]. In fact, a number of the issues required some
fairly significant refactoring of the state management components in
our JCR implementation. The original 0.6 plan, however, was include a
search and query feature. I've made a lot of progress with search/
query, but I still have a few weeks of completing the feature
development and integrating it with the connectors and JCR
implementation. There are also a number of outstanding issues that we
need/want to fix, so I'd guess we're still a month away from the
planned 0.6 release.
However, a number of people have taken a look at 0.5 recently, and
they've run into some of the same issues that we've already fixed.
They're currently using trunk, but have asked when the next stable
release will be available. We can either continue our current plans,
or change our schedule a bit and release 0.6 without the search/query
feature (or the fantastic Eclipse publishing plug-in). For the
record, we released 0.5 on June 11, and that's just under 3 months ago.
I'm leaning toward releasing 0.6 early and moving the search/query and
Eclipse features to the following release (which may actually be a 1.0
candidate). That would require me putting aside the search/query
stuff for a few days (maybe a week) so that I can focus on fixing a
number of the more critical and high-priority issues (we still have a
few TCK regressions that we should fix before releasing) and reviewing/
editing the documentation. But I think it's worth it so that we can
get another much more stable release out the door for people to use.
Please share your thoughts and comments. I would like to decide
within a day or two.
Best regards,
Randall
[1] https://jira.jboss.org/jira/browse/DNA?report=com.atlassian.jira.plugin.s...
15 years, 8 months
dna-jcr-gen - goal is to generate realistic and mass of test data for your system under test
by Serge Emmanuel Pagop
Hi altogether,
I start a small module dna-jcr-gen into the utils folder from the dna
parent project and the goal of the module is to help jcr developer for
generation of realistic and mass of data the system unter test.
dna-jcr-gen may also have to feature to export the generated content
to XML (Randall's wish) and my opinions are dna-jcr-gen can also use
during intergration testing and for performance testing.
Your Advise is welcome and already start a discussion with Randal
today and here is the copy of our discussion from #IRC client
sp__:Hi Randall!
[8:30pm]rhauch__:Hi, Serge! How are things going?
[8:30pm]sp__:rhauch__: great
[8:30pm]sp__:rhauch__: and you?
[8:32pm]sp__:rhauch: just inform me, if you get the email
[8:33pm]rhauch:what else is going on?
[8:34pm]sp__:rhauch: have you already take a look on the dna-jrc-gen
module?
[8:34pm]rhauch:no, not yet. i'm almost finished with this irritating
import issue. then i'll have a clean workspace and i'll take a look.
[8:35pm]sp__:rhauch: because I also need some advise, how we can make
that more dynamic
[8:36pm]rhauch:ah, okay. more dynamic ... meaning more easily used,
or more dynamically varying data?
[8:36pm]rhauch:or other?
[8:36pm]sp__:rhauch: I mean easily used
15 years, 8 months