On Oct 10, 2008, at 9:14 AM, Endre Stølsvik wrote:
> >> Just as another quick note, some dependency management tools will >> even >> support the levels of "snapshot" releases in this order: >> >> alpha >> beta >> milestone >> release candidate > > And then "release", I guess? > > However, milestones are before alpha. I've never seen a project using > the notion that a milestone is after beta. It kinda goes with the > word's meaning, even. > > Here's The Almighty Truth: > http://en.wikipedia.org/wiki/Software_release_life_cycle I'm not sure I'd say Wikipedia is the almighty truth, but I'll take a look and adjust Savant accordingly. I've seen a number of projects do milestones after alpha and beta. It really depends on the project. I tend to favor the word meanings. If you think of the meaning of the word milestone, it is a project date that you have reached. I tend to think that project dates are somewhat more definitive and stable than an alpha is. That's why I favor milestones after alpha and beta. I tend to think of alpha and beta as mostly broken but a flavor of what is to come. -bp --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
