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
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:
+1 for this :)
2014-02-17 10:10 GMT+01:00 Mark Struberg strub...@yahoo.de:
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
+1 Mark
2014-02-17 13:08 GMT+01:00 Ove Ranheim oranh...@gmail.com:
+1 for this :)
2014-02-17 10:10 GMT+01:00 Mark Struberg strub...@yahoo.de:
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
+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
.
LieGrue,
strub
- Original Message -
From: Gerhard Petracek gerhard.petra...@gmail.com
To: dev@deltaspike.apache.org
Cc:
Sent: Tuesday, 12 November 2013, 16:18
Subject: Re: [DISCUSS] next release version? 0.6 or 1.0?
@mark:
i never said that we should do #2.
regards
November 2013, 16:18
Subject: Re: [DISCUSS] next release version? 0.6 or 1.0?
@mark:
i never said that we should do #2.
regards,
gerhard
2013/11/12 Mark Struberg strub...@yahoo.de
Pete, Gerhard
The Problem here is that there are only 2 ways to handle the situation:
1
,
strub
From: Romain Manni-Bucau rmannibu...@gmail.com
To: Mark Struberg strub...@yahoo.de;
dev@deltaspike.apache.org
Sent: Monday, 11 November 2013, 20:54
Subject: Re: [DISCUSS] next release version? 0.6 or 1.0?
Well if code is released it should
+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!
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:
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
- Original Message -
From: Charles Moulliard ch0...@gmail.com
To: dev@deltaspike.apache.org
Cc: Mark Struberg strub...@yahoo.de
Sent: Monday, 11 November 2013, 18:25
Subject: Re: [DISCUSS] next release version? 0.6 or 1.0?
+1 to move to 1.0. We have
From: Pete Muir pm...@redhat.com
To: dev@deltaspike.apache.org
Sent: Tuesday, 12 November 2013, 14:35
Subject: Re: [DISCUSS] next release version? 0.6 or 1.0?
+1 to Gerhard’s point (I am looking to try to find someone to
help
with
docs, but the person I had in mind
andraschko.tho...@gmail.com
To: dev@deltaspike.apache.org
Cc:
Sent: Wednesday, 13 November 2013, 23:51
Subject: Re: [DISCUSS] next release version? 0.6 or 1.0?
@Romain:
I understand all your concerns - really!
But from the view of CODI users, the current situation is quite
disappointing
Message -
From: Thomas Andraschko andraschko.tho...@gmail.com
To: dev@deltaspike.apache.org
Cc:
Sent: Wednesday, 13 November 2013, 23:51
Subject: Re: [DISCUSS] next release version? 0.6 or 1.0?
@Romain:
I understand all your concerns - really!
But from the view of CODI users
:
Sent: Wednesday, 13 November 2013, 23:51
Subject: Re: [DISCUSS] next release version? 0.6 or 1.0?
@Romain:
I understand all your concerns - really!
But from the view of CODI users, the current situation is quite
disappointing because the most required CODI features are still
From: Pete Muir pm...@redhat.com
To: dev@deltaspike.apache.org
Sent: Tuesday, 12 November 2013, 14:35
Subject: Re: [DISCUSS] next release version? 0.6 or 1.0?
+1 to Gerhard’s point (I am looking to try to find someone to help with
docs, but the person I had
+1 for v1. If we don't go back (= we don't make unstable stable
modules) it is enough IMO
with later modules.
Thus I prefer 1.).
LieGrue,
strub
From: Pete Muir pm...@redhat.com
To: dev@deltaspike.apache.org
Sent: Tuesday, 12 November 2013, 14:35
Subject: Re: [DISCUSS] next release version? 0.6 or 1.0?
+1 to Gerhard’s point (I am looking
Message -
From: Gerhard Petracek gerhard.petra...@gmail.com
To: dev@deltaspike.apache.org
Cc:
Sent: Tuesday, 12 November 2013, 16:18
Subject: Re: [DISCUSS] next release version? 0.6 or 1.0?
@mark:
i never said that we should do #2.
regards,
gerhard
2013/11/12 Mark
November 2013, 16:18
Subject: Re: [DISCUSS] next release version? 0.6 or 1.0?
@mark:
i never said that we should do #2.
regards,
gerhard
2013/11/12 Mark Struberg strub...@yahoo.de
Pete, Gerhard
The Problem here is that there are only 2 ways to handle
Hi!
In the last 2 months I did a few conference talks and smaller presentations
(OpenBlend, W-JAX, ..) and always got the same questions: it's only a 0.x
version, so is it already stable? I don't like to use it in production with 0.x
And the actual answer is: well, core, cdictrl, etc are
Yep, agreed. Users care about the version #. I would recommend that if we
could release a 1.0 based on the current code base + some additional bug
fixes we'll get huge wins.
+1 to switching current to 1.0.0-SNAPSHOT.
On Mon, Nov 11, 2013 at 12:08 PM, Mark Struberg strub...@yahoo.de wrote:
@deltaspike.apache.org
Cc: Mark Struberg strub...@yahoo.de
Sent: Monday, 11 November 2013, 18:25
Subject: Re: [DISCUSS] next release version? 0.6 or 1.0?
+1 to move to 1.0. We have done the same thing with Apache Aries moving
Blueprint from 0.5 to 1.0 release
On Mon, Nov 11, 2013
24 matches
Mail list logo
