[hibernate-dev] Hibernate OGM: organize JIRA issues in components?

Emmanuel Bernard emmanuel at hibernate.org
Wed May 23 11:48:54 EDT 2012

What I'm saying is that, data stores are really 3 to 4 classes. Does it really warrant a full component for each?

On 22 mai 2012, at 18:24, Sanne Grinovero wrote:

> On 22 May 2012 16:22, Emmanuel Bernard <emmanuel at hibernate.org> wrote:
>> I almost did this a couple of time actually.
>> My rational for having datastore and not mongodb etc was that after the initial implementation, I expect few to no activity. If you think I am wrong, I'm fine with adding them as components.
> you are currently using it mostly for task-planning, but it will end
> up being used as an *issue* tracker, no?
> Unless nobody uses them.. so I hope they will be useful.
> Cheers,
> Sanne
>> On 21 mai 2012, at 23:27, Sanne Grinovero wrote:
>>> I'm tempted to create different components for each datastore, so we
>>> can easily classify them and search for areas:
>>> - ehcache
>>> - infinispan
>>> - mongodb
>>> - cassandra
>>> useful to understand the progress per area.. we can later add more components.
>>> Alternative, we could use labels.. but they are often too flexible,
>>> while in this case a single category is often a good fit.
>>> comments before I proceed?
>>> It's good for me to go through them, I just realized my mail filters
>>> were wiping out all changes I wasn't directly related with (unlike
>>> with Search) and I had no idea of some issues I'm seeing open now :-/
>>> Cheers,
>>> Sanne
>>> _______________________________________________
>>> hibernate-dev mailing list
>>> hibernate-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev

More information about the hibernate-dev mailing list