Jason van Zyl wrote:
Brett Porter wrote:
- RC's are the actual build. It will report version "2.0", and is
differentiated from the actual final release (if different), by the
build timestamp. If the RC is not suitable for any reason, we remove
the old tag, and redo the release
Can you expand on this and possibly through series
of version names to illustrate the movement toward a release?
I may be getting ahead of myself :)
as far as pom goes:
2.1-SNAPSHOT
2.1-alpha
2.1-SNAPSHOT
2.1-beta-1
2.1-SNAPSHOT
2.1
where 2.1 gets put out as 2.1 RC1, and renamed 2.1 when it is tested as
good.
The goal is to not rebuild code that was tested as an RC for a couple of
reasons:
- so you release what you actually test
- to avoid risk of environmental factors producing a different output to
what was tested
- to save work in going through the release process all over
The problem with this, which was an issue in the 2.0 release, was that
the 2.0 JARs get deployed as part of the process and are now "out there"
in the repository.
I think the solution to this is for snapshots, alphas, betas and rcs to
all be deployed to the development repository, and only after successful
testing be moved to the release repository (so ibiblio wouldn't have
alpha and beta code in the same way it doesn't have snapshots). The
problem is that we can't do that just yet :)
We have another issue - because Maven operates off the repository, it
needs to find all its JARs. This entails putting the development
repository into the configuration for the distribution (I think in a
profile in $M2_HOME/conf is probably more appropriate than the super
POM), but this won't work for the RC - maybe the RC requires a manual
step by the user to test for this case.
Anyway, we aren't quite there yet, so I'll step this back and say we
just rebuild/tag as usual for an RC and for the final (where the final
shouldn't have any changes since the last RC). I think doing the above
repository step is possibly a good idea though.
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
