Re: Advice on version control

Wed, 16 Jun 2010 21:28:41 -0700 

On 15/06/2010 9:04 AM, Eric Rotick wrote:

All good advice but my feeling is that is all comes down to one basic rule;
if it can go wrong, it will.
Yes but it your systems should reduce the chance of it getting worse. A lot of cached releases in local Maven repos that are incorrect will cause a lot of chaos. 


We've all been there; the code's written, the documentation's done and it's
just about to go out the door when someone spots something. The project lead
looks at it and decides it's a minor change and won't upset anything.
There's the problem. When the pressure is on, you make these silly mistakes.
If there was something that really did stop the re-release of a non snapshot
project then it has to be done by the book and the mistake avoided.

Even the additional work to bump other versions must be better than the
application failing. I know there will always be the occasion when the
change really is minor, like in say documentation and you could have gotten
away with it but I would certainly prefer that there was a 'machine' waiting
patiently to stop things like this in their tracks.

I'm going to see if Nexus really is that quick to install. Of course, it's a
bit late now!


On Tue, Jun 15, 2010 at 1:52 PM, Jeff Jensen<
[email protected]>  wrote:


And the release plugin does the version number changes (from snapshot to
release, commit POM, bump to next snapshot version, commit) for you...
I wonder if using it would help your process consistency by eliminating a
few manual things.


-----Original Message-----
From: Adrian Shum [mailto:[email protected]]
Sent: Tuesday, June 15, 2010 7:42 AM
To: Maven Users List
Subject: RE: Advice on version control

I think the main point is: after release, change the POM version
immediately to
snapshot again.  By doing so, people shouldn't re-release accidentally
(They will only re-release a snapshot, which is harmless), unless they
explicitly
change the POM version and re-release themselves.

I think it is more of a procedure issue instead  :)

--
Best Regards,
AdRiAN ShUM


-----Original Message-----
From: Eric Rotick [mailto:[email protected]]
Sent: Tuesday, June 15, 2010 7:53 PM
To: Maven Users List
Subject: Re: Advice on version control


This is exactly what we've been doing and it's been working well for
years but we now realise it's very fragile. The change that broke the
system was seemingly benign and the project lead also though so but in
reality it was not. If the policy of single releases only for non
snapshots was enforced then the other elements would have required a
minimum of a version bump and the system would still be fine.

I've often wondered why we needed a repo manager and now I know ;-)

On Tue, Jun 15, 2010 at 12:38 PM, Adrian Shum<[email protected]>
wrote:


Here is the practice I am adopting now:

Whenever the project is open for change,
use SNAPSHOT version.

Change the version to a concrete version
number when you decide to perform a release.
Do your release branching and tagging etc,
and then immediate change the POM version
back to SNAPSHOT.

i.e. whenever a project source is subject to
change, use SNAPSHOT as version in POM

--
Best Regards,
AdRiAN ShUM


-----Original Message-----
From: Eric Rotick [mailto:[email protected]]
Sent: Tuesday, June 15, 2010 7:22 PM
To: [email protected]
Subject: Advice on version control


This might be more to do with SCM than Maven but as Maven seems to
have the handle on most things I thought I'd ask this list first.

It is clear that the version contained in the pom is vitally important

and the process by which a version or revision number is incremented
is clear. Unfortunately, someone made a mistake of making a
significant change to some source and re-released the jars without
changing the version. The result was that the client application would

not talk to the server in certain conditions.

Basically, given our current procedures, this was a problem waiting to

happen.

Although it is clear what needs to happen it eludes us how this is
enforced. It seems that we need the ability to write snapshots any
number of times but non snapshots can only be written once and then no

more.

Hmm, I've just thought, maybe this is what the likes of Nexus and
Artifactory would do, but as you've probably guessed we don't use
anything like this.

Could anyone offer advice or practices to stop this happening again.

Thanks.

This email is confidential. If you are not the intended recipient,
please delete it from your system and notify the sender immediately.
Any unauthorized use, disclosure, dissemination or copying of this
email is prohibited. Taifook Securities Group, its group companies and

their content providers ("Parties") shall not be responsible for the
accuracy or completeness of this email or its attachment, if any,
which could contain virus, be corrupted, destroyed, incomplete,

intercepted, lost or arrive

late.   The Parties do not accept liability for any damage caused by

this

email.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



This email is confidential. If you are not the intended recipient, please
delete it from your system and notify the sender immediately. Any
unauthorized use, disclosure, dissemination or copying of this email is
prohibited. Taifook Securities Group, its group companies and their content
providers ("Parties") shall not be responsible for the accuracy or
completeness of this email or its attachment, if any, which could contain
virus, be corrupted, destroyed, incomplete, intercepted, lost or arrive
late.   The Parties do not accept liability for any damage caused by this
email.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to