My fear is that if they cut 2.0 for the sake of getting it out the
door as soon as possible, a lot of other good features will have to wait
another 2-3 years until Guice 3.0. If you guys are planning on releasing
a Guice update once every 6 months then I agree you should cut 2.0 soon,
but otherwise please take your time :)
Gili
Endre Stølsvik wrote:
> On Thu, Oct 9, 2008 at 11:41 PM, Bob Lee <[EMAIL PROTECTED]> wrote:
>
>> Guice core is small and a bit intricate internally, so it doesn't make sense
>> for a lot of people to work on it.
>>
>
> Shouldn't these few people working on it cut a new release soon, then?
> There are lots of wishes in the issue tracker, and folks are eagerly
> awaiting new features. Prudence in regard to introducing new code is
> good - to a degree: Guice 1.0 has been the sole release for a while
> now. Hearing that Google internally uses a much newer version is a bit
> annoying: Why not make it into a proper release so that us on the
> outside can use it with some confidence too? There are furthermore
> several patches submitted (e.g. the string of patches from James
> Strachan lately, and several in the issue tracker), thus at least some
> people seem to understand the code.
>
> Thanks,
> Endre.
>
> >
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"google-guice" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-guice?hl=en
-~----------~----~----~----~------~----~------~--~---
