+1
On Mon, Feb 17, 2014 at 2:10 AM, Mark Struberg <strub...@yahoo.de> wrote: > Oki, I can help a bit with ViewAccessScoped. Romain and Thomas, please fix > the Tx stuff. > > In that case I'd say we gonna ship a 0.6 and then in 3 weeks move to 1.0. > > wdyt? > > > LieGrue, > strub > > > > > > On Monday, 17 February 2014, 10:06, Romain Manni-Bucau > <rmannibu...@gmail.com> wrote: > > Hi >> >> >>can we wait 1 or 2 weeks (no more) to see if we can sort out @Repo/@Tx >>stuff? Basically I'm waiting after it for months and this is blocker >>to be used ATM. >>Romain Manni-Bucau >>Twitter: @rmannibucau >>Blog: http://rmannibucau.wordpress.com/ >>LinkedIn: http://fr.linkedin.com/in/rmannibucau >>Github: https://github.com/rmannibucau >> >> >> >> >>2014-02-17 9:57 GMT+01:00 Mark Struberg <strub...@yahoo.de>: >>> back 2 the topic, please! >>> >>> I'd say we should approach 1.0 NOW. >>> >>> DeltaSpike core and a few other modules is really rock solid already since >>> a year or so. It is also used heavily in production already. >>> There will always be some modules which are not so perfectly mature at >>> times. E.g. if we will add a new module. >>> >>> Thus I already did propose a methology which would fix this shortcoming: >>> We might introduce an 'ample page' which contains the status of each >>> project - stable / ready /in progress >>> >>> You know, the traffic light thingy where green means the module (e.g. >>> deltaspike-core) is stable and the API will not change or we will at least >>> be backward compatible unless we do a major new version. >>> Orange means that the module has been tested and looks good. Whereas red >>> means that the api might change still. >>> >>> What road blockers do we have before 1.0? >>> Please note that there is always something one can do better - but this >>> should not hinder us from releasing until something is really broken. >>> Also the documentation is *not* a show stopper - it is perfectly fine to >>> ship this later as our CMS is completely asynchronous. >>> >>> >>> So what BLOCKERS do you see before I go and press the release button? >>> Like to do that on Wednesday... >>> >>> >>> LieGrue, >>> strub >>> >>> >>> >>> >>> On Sunday, 16 February 2014, 23:14, Ove Ranheim <oranh...@gmail.com> wrote: >>> >>> That's reasonable enough. >>>> >>>> >>>>On 16. feb. 2014, at 23:02, Jason Porter <lightguard...@gmail.com> wrote: >>>> >>>>> Probably because we've become busy with some other projects and >>>>> priorities :(-- >>>>> Sent from Mailbox for iPhone >>>>> >>>>> On Sun, Feb 16, 2014 at 2:39 PM, Ove Ranheim <oranh...@gmail.com> wrote: >>>>> >>>>>> The commit graph shows too few committers.. and I appreciate your work! >>>>>> I also notice too few Redhat/JBoss Weld/Seam committers left on the >>>>>> project. How come? >>>>>> /ove >>>>>> On 16. feb. 2014, at 22:10, Gerhard Petracek >>>>>> <gerhard.petra...@gmail.com> wrote: >>>>>>> hi ove, >>>>>>> >>>>>>> i was only talking about the commits. >>>>>>> >>>>>>> regards, >>>>>>> gerhard >>>>>>> >>>>>>> http://www.irian.at >>>>>>> >>>>>>> Your JSF/JavaEE powerhouse - >>>>>>> JavaEE Consulting, Development and >>>>>>> Courses in English and German >>>>>>> >>>>>>> Professional Support for Apache MyFaces >>>>>>> >>>>>>> >>>>>>> >>>>>>> 2014-02-16 22:07 GMT+01:00 Thomas Andraschko >>>>>>> <andraschko.tho...@gmail.com>: >>>>>>> >>>>>>>> +1 Ove >>>>>>>> We are really late for an 0.6. I would release 0.6 this/next month and >>>>>>>> after that, lets finish 1.0. >>>>>>>> We should fix all open issues and finish the documentation! >>>> >>>> >>>> >> >> >>
