Note, wait-and-talk-to-mark is essentially option C as Mark isn't back from JAX 
till next week.

So far option B seems the dominant choice.  I'll get started with that and try 
and get some binaries up for tire-kicking then go to bed.


-David

On Nov 7, 2013, at 9:58 PM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote:

> Ping Mark to know what is the openjpa regression. If blocking wait openjpa
> (or do the fix), if not B (or with the fix in our fork)...
> 
> I just dont want a blind release
> Le 7 nov. 2013 22:38, "Alex The Rocker" <alex.m3...@gmail.com> a écrit :
> 
>> +1 for option B, and I like the idea of a 1.6.1 maintenance release with
>> OpenJPA final in it, that's a perfect one if option B can be provided super
>> fast (this week at least as a release candidate)
>> 
>> Otherwise it'll amount to option C for us :(
>> 
>> Thanks
>> Alex
>> 
>> 
>> 
>> On Thu, Nov 7, 2013 at 10:32 PM, Jean-Louis MONTEIRO <jeano...@gmail.com
>>> wrote:
>> 
>>> Need to check whereas the option A is possible.
>>> 
>>> I'm for B, but I would add the following: release 1.6.1 release
>> maintenance
>>> as soon as OpenJPA gets released. Release maintenance only, no new
>>> features. Only big bugfixes and dep updates.
>>> 
>>> Latest option is not acceptable for me
>>> 
>>> To summarize:
>>> A = 0
>>> B = +1
>>> C = -1
>>> 
>>> 
>>> JLouis
>>> 
>>> 
>>> 2013/11/7 David Blevins <david.blev...@gmail.com>
>>> 
>>>> So we need to start getting builds for Alex, Tim, Judah and crew or
>> they
>>>> won't be able to move forward with TomEE.
>>>> 
>>>> We just have the OpenJPA issue to deal with.  We have two options:
>>>> 
>>>> A. Release with OpenJPA 2.2.2
>>>> B. Release with OpenJPA 2.3.0 "pre" build of our creation -- we've
>> done
>>>> this with other things before on rare occasion
>>>> 
>>>> Of course there is a 3rd option:
>>>> 
>>>> C. Forget those guys, they should give us more than 4 months lead time
>>>> that they'll need a release.
>>>> 
>>>> I personally don't feel good about option #3.  Would hang those guys
>> out
>>>> to dry and send a very bad message to other users.  We need to get that
>>>> frequent release thing down.
>>>> 
>>>> So which option would have your vote?
>>>> 
>>>> 
>>>> -David
>>>> 
>>>> On Nov 3, 2013, at 10:22 PM, Mark Struberg <strub...@yahoo.de> wrote:
>>>> 
>>>>> openjpa-2.2.2 uses a hardcoded asm-3.2 dependency. That pretty much
>>>> sucks.
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>> ________________________________
>>>>>> From: David Blevins <david.blev...@gmail.com>
>>>>>> To: dev@tomee.apache.org
>>>>>> Sent: Monday, 4 November 2013, 3:25
>>>>>> Subject: Re: Time to release TomEE 1.6.0
>>>>>> 
>>>>>> 
>>>>>> Branched in hopes we can kick out some of the snapshot dependencies
>> we
>>>> have and get a release candidate up mid week -- or at least something
>>>> people can beat on.
>>>>>> 
>>>>>> In terms of OpenJPA specifically, what is the exact issue with using
>>>> 2.2.2?
>>>>>> 
>>>>>> 
>>>>>> -David
>>>>>> 
>>>>>> 
>>>>>> On Oct 8, 2013, at 5:00 PM, David Blevins <david.blev...@gmail.com>
>>>> wrote:
>>>>>> 
>>>>>>> I pinged a few people on the OpenJPA release prior to JavaOne.
>> Mark
>>>> had volunteered some personal time for doing the OpenJPA release we
>> need.
>>>> Mark, that still something you're up for doing?
>>>>>>> 
>>>>>>> 
>>>>>>> -David
>>>>>>> 
>>>>>>> On Sep 5, 2013, at 3:52 AM, Jean-Louis MONTEIRO <
>> jeano...@gmail.com>
>>>> wrote:
>>>>>>> 
>>>>>>>> Cool, thanks!
>>>>>>>> 
>>>>>>>> Will send a mail to dev@openwebbeans.
>>>>>>>> 
>>>>>>>> JLouis
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 2013/9/5 Romain Manni-Bucau <rmannibu...@gmail.com>
>>>>>>>> 
>>>>>>>>> FYI: TCK and build are back to green so only the dep issue now
>>>> (thanks
>>>>>>>>> David for TCK report)
>>>>>>>>> 
>>>>>>>>> *Romain Manni-Bucau*
>>>>>>>>> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>>>>>>>>> *Blog: **http://rmannibucau.wordpress.com/*<
>>>>>>>>> http://rmannibucau.wordpress.com/>
>>>>>>>>> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>>>>>>>>> *Github: https://github.com/rmannibucau*
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 2013/9/4 Jean-Louis MONTEIRO <jeano...@gmail.com>
>>>>>>>>> 
>>>>>>>>>> I know that almost everybody is currently working in production
>>> with
>>>>>>>>>> SNAPSHOTS (kinda releases for OpenEJB).
>>>>>>>>>> But sometimes, it's also good to take time to product real
>>> releases.
>>>>>>>>>> 
>>>>>>>>>> But, fully agree with you. Right now it a bit complicated
>>> regarding
>>>> the
>>>>>>>>>> community.
>>>>>>>>>> Hopefully, that should be better in coming weeks, months cause
>> we
>>>> are
>>>>>>>>>> seeing more and more contributors on the mailing lists.
>>>>>>>>>> 
>>>>>>>>>> So they should join the committers' list of the project.
>>>>>>>>>> 
>>>>>>>>>> JLouis
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 2013/9/4 Romain Manni-Bucau <rmannibu...@gmail.com>
>>>>>>>>>> 
>>>>>>>>>>> Hehe,
>>>>>>>>>>> 
>>>>>>>>>>> I hope so too but *today* it seems too complicated so i prefer
>> to
>>>> be
>>>>>>>>>>> realistic.
>>>>>>>>>>> Le 4 sept. 2013 15:48, "Jean-Louis MONTEIRO" <
>> jeano...@gmail.com
>>>> 
>>>> a
>>>>>>>>>> écrit
>>>>>>>>>>> :
>>>>>>>>>>> 
>>>>>>>>>>>> Without moving from one side to the opposite, we can IMO do
>>> better
>>>>>>>>> and
>>>>>>>>>>> more
>>>>>>>>>>>> frequent releases, at least with bugfixes.
>>>>>>>>>>>> 
>>>>>>>>>>>> JLouis
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 2013/9/4 Romain Manni-Bucau <rmannibu...@gmail.com>
>>>>>>>>>>>> 
>>>>>>>>>>>>> arquillian update/fix is done for weeks, OpenJPA guys doesn't
>>>> move
>>>>>>>>>> but
>>>>>>>>>>> we
>>>>>>>>>>>>> can fork even if that's a bit sad, OWB is not an issue IMO
>> (we
>>>> just
>>>>>>>>>>> need
>>>>>>>>>>>> to
>>>>>>>>>>>>> ask).
>>>>>>>>>>>>> 
>>>>>>>>>>>>> However our TCKs report is broken (report, not TCKs themself
>> ;)
>>>> so
>>>>>>>>> we
>>>>>>>>>>>> need
>>>>>>>>>>>>> it to be fixed before any release.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> About maintenance releases: I think it is clear we are not
>> able
>>>> to
>>>>>>>>> do
>>>>>>>>>>> so.
>>>>>>>>>>>>> So when somebody able to release is ready to do it, let's
>> just
>>>>>>>>>> release
>>>>>>>>>>>> IMO.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> *Romain Manni-Bucau*
>>>>>>>>>>>>> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>>>>>>>>>>>>> *Blog: **http://rmannibucau.wordpress.com/*<
>>>>>>>>>>>>> http://rmannibucau.wordpress.com/>
>>>>>>>>>>>>> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>>>>>>>>>>>>> *Github: https://github.com/rmannibucau*
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 2013/9/4 Jean-Louis MONTEIRO <jeano...@gmail.com>
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> @tiklu TomEE depends on other implementations to implement
>>> Java
>>>>>>>>> EE
>>>>>>>>>> 7.
>>>>>>>>>>>> The
>>>>>>>>>>>>>> work has already started with openwebbeans and bean
>>> validation.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Well regarding our 1.6.0 release, I would like to have it by
>>> the
>>>>>>>>>> end
>>>>>>>>>>> of
>>>>>>>>>>>>>> September.
>>>>>>>>>>>>>> Any updates on Arquillian, OpenWebBeans and OpenJPA?
>>>>>>>>>>>>>> Are they absolutely necessary?
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> If API changes, ok if just a bugfix, mais be we can release
>>>>>>>>> another
>>>>>>>>>>>>>> maintenance release next month with new dependency updates.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> any comment?
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> JLouis
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 2013/7/18 tiklu ganguly <tiklugang...@gmail.com>
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> and when are you guys planning support for JavaEE 7?
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On Thu, Jul 18, 2013 at 9:25 AM, Romain Manni-Bucau
>>>>>>>>>>>>>>> <rmannibu...@gmail.com>wrote:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> PS we need arquillian 1.1.1.Final too to remove an ugly
>> hack
>>>>>>>>> we
>>>>>>>>>>>> have
>>>>>>>>>>>>>> ATM,
>>>>>>>>>>>>>>>> normally should be here at the end of the week
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> *Romain Manni-Bucau*
>>>>>>>>>>>>>>>> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>>>>>>>>>>>>>>>> *Blog: **http://rmannibucau.wordpress.com/*<
>>>>>>>>>>>>>>>> http://rmannibucau.wordpress.com/>
>>>>>>>>>>>>>>>> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>>>>>>>>>>>>>>>> *Github: https://github.com/rmannibucau*
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 2013/7/16 Romain Manni-Bucau <rmannibu...@gmail.com>
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> We are still waiting for owb 1.2.1 and openjpa 2.3 :(
>>>>>>>>>>>>>>>>> Le 16 juil. 2013 15:26, "Jean-Louis MONTEIRO" <
>>>>>>>>>>>> jeano...@gmail.com>
>>>>>>>>>>>>> a
>>>>>>>>>>>>>>>>> écrit :
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Hey guys,
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> was wondering if we could release TomEE 1.6.0.
>>>>>>>>>>>>>>>>>> Is there any other releases we have to wait for?
>>>>>>>>>>>>>>>>>> Does anybody has important things in progress?
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> It's been a very long time since latest release and it's
>>>>>>>>>>>> necessary
>>>>>>>>>>>>>> in
>>>>>>>>>>>>>>> my
>>>>>>>>>>>>>>>>>> opinion to get it out soon now.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Any thoughts?
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Jean-Louis
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Jean-Louis
>>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> --
>>>>>>>>>>>> Jean-Louis
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> --
>>>>>>>>>> Jean-Louis
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> --
>>>>>>>> Jean-Louis
>>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> Jean-Louis
>>> 
>> 

Reply via email to