Jesse,
What do you think of the following versioning scheme and associated
schedule?
"major.minor.build" (i.e. Guice 1.2.3)
- where "major" represents a release that contains major API breaks
(i.e. major refactoring) released every 2-3 years
- where "minor" represents a release that contains minor API breaks
(i.e. new functionality) released every 6 months to a year
- where "build" represents a release that contains bug fixes and changes
that are fully backwards-compatible with the current minor release
(released every 3 months)
Gili
[EMAIL PROTECTED] wrote:
> Internally we're able to use something newer
> than 1.0 because we're willing to cope with
> incompatible API changes. This is a lot of
> work, but we bear it to get access to features
> that are still under development.
>
> If you're willing to deal with an API that
> is still unstable, I invite you to use the
> snapshots.
>
> I'm working very hard on the 2.0 release,
> but there's a huge amount of work involved
> to deliver a release with the quality and
> stability you can depend on.
> >
>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
