On Mar 20, 2007, at 7:56 PM, Mohammad Nour El-Din wrote:
Hi Dain...
I like your idea, but IMHO I think we have to wait until we make
sure that
the minimum set of EJB3.0 features are implemented, by examining
the list
provided by DBlevins. Then we can make the OEJB3.0 release out to
the light.
We should probably go through that list and decide what the must
haves are and what we can do without.
For example, IMHO we can do without the Validation, iTests, and
Examples sections. We could definitely work on the validation part
while people are giving us some initial feedback on the release
content overall. I suspect user feedback might also how we
prioritize completing the itests.
Might be some other ones that aren't critical too.
-David
On 3/21/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
I think we should just ship what we have now as "3.0". We have tons
of new exciting stuff and people can start working with it. As they
find issues we can release updates.
I've been mainly working on the 2.x stuff and it is pretty close to
be fully complete, but I don't think it is worth waiting around for
some infrequently used features to be finished.
-dain
On Mar 16, 2007, at 4:15 PM, David Blevins wrote:
> I've been wondering when we should start kicking some releases from
> the 3x branch out the door. I can't seem to come up with a good
> answer even in my own mind about when this should be.
>
> Seems we're doing really great as far as functionality and
> implementing EJB3 is concerned. We still have a ways to go, but
> not too far actually.
>
>
> Should we start shipping releases? If so what do we call them and
> when do we start? If not what do we need to get done?
>
>
> Thoughts? (floor's open to all, committer or not)
>
>
> -David
>
>
--
Thanks
- Mohammad Nour
