Sent from my [rhymes with tryPod] ;-)
On 25 Oct 2009, at 01:36, David Weintraub qazw...@gmail.com wrote:
No one has answered the basic question: Why two repositories?
I know the differences between a release and snapshot. but that
doesn't
explain why the releases and snapshots are in two
On Sun, Oct 25, 2009 at 7:27 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
So, what is the reason to have two separate and distinct repositories for
snapshots and for releases?
update frequency, you may want to check snapshots with a greater or lesser
frequency than releases
2009/10/25 Stephen Connolly stephen.alan.conno...@gmail.com:
Sent from my [rhymes with tryPod] ;-)
On 25 Oct 2009, at 01:36, David Weintraub qazw...@gmail.com wrote:
No one has answered the basic question: Why two repositories?
I know the differences between a release and snapshot. but
On Sat, Oct 24, 2009 at 9:36 PM, David Weintraub qazw...@gmail.com wrote:
No one has answered the basic question: Why two repositories?
I know the differences between a release and snapshot. but that doesn't
explain why the releases and snapshots are in two separate repositories.
Why
not
That's certainly seems like one good reason...
Another reason is that your unreleased snapshots are going to trash
your release repository... This, of course, depends on how you
build...
For example, on our project, I didn't at first care to use the
snapshots repository and just had everything
No one has answered the basic question: Why two repositories?
I know the differences between a release and snapshot. but that doesn't
explain why the releases and snapshots are in two separate repositories. Why
not keep both snapshots and releases in the same repository. We know
something is a
Sometime back I had the exact question in my mind and QoS (what you
mentioned as administration) and security were the only ones I could
think of.
Thanks,
Sahoo
David Weintraub wrote:
No one has answered the basic question: Why two repositories?
I know the differences between a release and
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
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
a snapshot usually has no guarantee of passing any sort of testits 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
On Thu, Oct 22, 2009 at 9:45 AM, Martin Gainty mgai...@hotmail.com wrote:
a snapshot usually has no guarantee of passing any sort of testits a way
for a programmer/developer to prove
that the developer assigned has done *something*..but the snapshot carries no
guarantee has passed
Very interesting discussion. We have been having some of the exact same
discussions.
A lot of it comes down to what one defines as a team. Is a team a
collection of 3 developers working on a very specific part of a larger
system? Or, on the complete other side of the spectrum, is it 100
12 matches
Mail list logo
