On Tue, Sep 9, 2008 at 10:37 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>wrote:

> The code has come a long, long way since
> Guice 1.0 and I'd quite like it if we could
> get something of release quality out for
> folks to start using. I'm thinking of polishing
> up the current code (Javadocs, etc.) and
> calling it 'Guice 2.0'.
>
> Even without the new features it's still a
> huge update, and worthy of your time to
> upgrade. (hello, @Provides)
>
> Once that's available, I'll keep working, and
> get Guice 2.1 out during 'fall 2008'. This
> should contain all of the slipped features.
>

Let's not try to rush a release out on such short notice. "Summer 2008" was
just a random date we pulled out of our asses.

I know everyone is excited about 2.0, but we're in no danger of slipping
perpetually. We have a concrete, minimal list of features we plan on
including. We should take as much time as is necessary to polish and
document those features because it goes without saying, we will be stuck
with them indefinitely.

We need to build some real extensions on top of the new features before I'll
be comfortable rubber stamping them. For example, I'd like to see a scope
validator and maybe even an update to our Eclipse plugin.

As for the version number, this feels like a 2.0 to me.

Finally, I think I should take on hierarchical injectors. This is sticky
territory. To those who are afraid the feature will be confusing, we could
only expose hierarchical injectors through the SPI. For example, instead of
creating a child injector through Guice.createInjector(), you could call
com.google.inject.spi.HierarchicalInjectors.create(Injector parent, ...).

Bob

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to