I felt quite comfortable with using the tags from svn. A simple guice-2.0-09082008 Snapshot tag would do well for me. Anybody who wants can execute the build, create the jar and deploy it to wherever he/she wants to (for me it'd be the maven repository :-)). Google collections handle that somehow like this I think.
Georg On 10 Sep., 22:30, Marko Kocić <[EMAIL PROTECTED]> wrote: > On 10 сеп, 21:36, "Bob Lee" <[EMAIL PROTECTED]> wrote: > > > On Tue, Sep 9, 2008 at 10:37 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>wrote: > > > 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. > > Agree. Let's better 2.0 be rock solid, since it will going to have a > lot of press. > > > 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. > > That's why 2.0 beta/alpha is important. Doing 2.0 without a single > prerelease will not get much testing of new features from the users. > Random snapshots are just not enough. > > > 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. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
