Reported by hlship, May 04, 2009
The version.properties in the 1.0 branch generates snapshot releases.
Ideally, there should be a tags/1.0 branch that locks down the 1.0 release.
Context: trying to build a 1.0 release artifact for the Maven repository.
Comment 1 by richhickey, May 04, 2009
Do you believe this advice was erroneous?
Comment 2 by hlship, May 05, 2009
I'm bothered that the 1.0 release is a 1.0 release, but not really. Either its a
final release or its not. Saying its still a snapshot when you've broadcasted to the
world that its final seems very odd to me.
On the mailing list, I espoused the "Apache Way", which is to not get hung up on a
"1.0.0" number, but keep releasing. If "1.0.2" has bugs, fix them and release
"1.0.3". If that is finally stable, announce "Clojure 1.0 is version 1.0.3". Let the
release prove itself valid.
Older Tapestry releases were based on the "line in the sand" approach ... and always
ended up requiring a flurry of dot release bug fixes.