>>> I can do a release. Just wondering whether it should be a CR already? >>> The main point of 4.5 was to give us ORM 4.3 compatibility, right? AFAIK we >>> already upgraded now >>> to 4.3.0.Final (just not released yet). So it would really be time to get >>> 4.5.0.Final out. >>> We could cut a CR release and if nothing comes up promote it to 4.5 final >>> in a couple of weeks. >> >> We also have the Infinispan indexmanager on the roadmap. All work was >> done a year ago already, and the Infinispan issues which prevented me >> to merge it at the time are fixed, so I should only need to rebase it. >> >> I would love to merge it, but let's set a deadline for it.. if I can't >> make it we release without it again :-( >> >> Also I'm worried about HSEARCH-1260 and Guillaume's report. It would >> be nice to get rid of those issues by applying the cleanup I've >> suggested on that thread. >> >> I fundamentally agree that if we don't address these quickly, we >> should aim at a quick Final, still let's not rush it too much as >> WildFly doesn't stricly need a Final from us (or at least I wasn't >> asked for one). > > Don’t you think that a lot of users might hold of an upgrade, because they > want a final > or at least CR release? If we want people to use 4.5 we might need to give > them > a final sooner than later. I don’t see the mentioned issues addressed in the > near > future. Guillaume for example won’t be able to look at the mass indexer until > some > time February. Is it in this case not better to do a 4.5.0.Final and then add > the > mentioned features in a 4.5.x release?
Have we decided on a version? Sanne, you still vote for a 4.5 Beta1? —Hardy _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
