a snapshot usually has no guarantee of passing any sort of test....its a way 
for a programmer/developer to prove
that the developer assigned has done *something*..but the snapshot carries no 
guarantee has passed completely thru the SDLC validation lifecycle

a release carries much more weight..basically

all resources are identified and present and are of the correct version
the entire project will compile and 'build' usually to a war/ear/jar or to a 
zip/bz/tar or self-extracting jar
ALL of the <n/http/j>unit, regression and integration tests have been executed 
and verified that the code contained within does what its supposed to do
(usually specified in ReleaseNotes.html)
the next step for a build manager is to call for GA (general acceptance) which 
involves a formal signoff from all who test the product
the developer may or may not override a decision on a *failed* feature 
depending on a vote of whether that feature should be pushed to the next release

anyone else?
Martin 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




> From: bri...@infinity.nu
> Date: Thu, 22 Oct 2009 08:03:37 -0400
> Subject: Re: Why are repositories usually separated into releases and         
> snapshots?
> To: users@maven.apache.org
> 
> It's essentially because of what you wrote below. You may want to be
> very diligent about backing up your release repo, but not so rigorous
> for snapshots. Snapshots tend to take up a lot more disk than releases
> because there are many copies of it when you use timestamps. This
> requires cleanup and metadata update at times. The less often you
> touch your release repo to start removing and changing things, the
> safer the data there is.
> 
> On Thu, Oct 22, 2009 at 4:43 AM, Costin Caraivan <ccarai...@axway.com> wrote:
> >
> > Hello,
> >
> > I saw that most repositories are separated into releases and snapshots. And
> > that most repository managers recommend using releases and snapshots.
> >
> > Now, I know what each of them is:
> > 1. release -> stable version, will be uploaded only once, when you want to
> > change something you make a new release.
> > 2. snapshots -> development version, usually overwritten (you can keep
> > multiple snapshots, but it's not usually done)
> >
> > What are the benefits of having 2 separate repos? Cons & pros. Pros & cons
> > :)
> > --
> > View this message in context: 
> > http://www.nabble.com/Why-are-repositories-usually-separated-into-releases-and-snapshots--tp26006147p26006147.html
> > Sent from the Maven - Users mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
                                          
_________________________________________________________________
Windows 7: Simplify your PC. Learn more.
http://www.microsoft.com/Windows/windows-7/default.aspx?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen1:102009

Reply via email to