Release fast release often

[GoogleCodeExporter]

the last release of Spock was 2 years ago.  I personally have been using 
1.0-Snapshot for a while now. There are already some features that work fine. 

In total it would justify a 0.8 release so why not doing one?

Original issue reported on code.google.com by Bauer.Va...@gmail.com on 9 Nov 2014 at 9:49

[GoogleCodeExporter]

This *really* pisses me off. Spock is by far the best* testing framework for 
Java/Groovy, but this de facto absence of proper release cycle is totally 
destroying it in the eyes of developers. There’s still active (although slow) 
development, so I can’t understand why the hell Peter refuses to tag the 
version. Argh.

How can anyone convince other people to use it when the latest release is 2+ 
years old?!

* And IMHO the only really usable – JUnit/TestNG is totally unusable crap.

Original comment by ja...@jirutka.cz on 11 Dec 2014 at 11:32

[GoogleCodeExporter]

If it's good enough for Netflix et. al., chances are it's good enough for your 
team as well. Getting involved in the project might help as well. It would be 
great to have a release pipeline similar to that of Mockito, which helped them 
to overcome a 2+ year period in which they didn't have a single release. 
Despite that, I think that Mockito is still being used.

Original comment by pnied...@gmail.com on 11 Dec 2014 at 11:59

[GoogleCodeExporter]

OMG, I can’t believe it… releasing is not a rocket science! It’s just 
about running few commands *. What’s the problem? If it’s just about 
configuring Gradle for deploying to Maven Central (I thought that it’s 
already done), then it’ll be my greatest pleasure to do it.

I’m very sorry for my aggressive tone, but it’s really bothering me a lot. 
It’s so simple thing… :(

* Well, and writing a changelog, but forget it, it’s better to have a 
properly tagged version even without changelog than depending on one SNAPSHOT 
versions for years.

Original comment by ja...@jirutka.cz on 12 Dec 2014 at 12:19

[GoogleCodeExporter]

Obviously it's about more than that. It's about making it trivial to release at 
any time, not about making one more manual release.

Original comment by pnied...@gmail.com on 12 Dec 2014 at 12:31

[GoogleCodeExporter]

Okay, I‘ll look at it during Christmas. Do you already have access to the 
Maven Central (e.g. via Sonatype OSS)?

Original comment by ja...@jirutka.cz on 12 Dec 2014 at 12:37

[GoogleCodeExporter]

Yes, publishing to Maven Central is automated in the Gradle build. Check out 
Szczepan Faber's blog posts on releasing Mockito.

Original comment by pnied...@gmail.com on 12 Dec 2014 at 12:41

[GoogleCodeExporter]

I’m confused now… Is publishing Spock to Maven Central already automated 
using Gradle, or not? o.O

Original comment by ja...@jirutka.cz on 12 Dec 2014 at 12:59

[GoogleCodeExporter]

Publishing to Maven Central from a local dev box is automated. Doing a great 
release takes much more (read the blog posts).

Original comment by pnied...@gmail.com on 12 Dec 2014 at 1:00

[GoogleCodeExporter]

We don’t need a perfect release — any release will be good enough than no 
release! If you have already automated it, so you can just run one command to 
build and deploy artifacts to Maven Central, than where the hell is problem?

Yes, it’s good to have a perfect continuous delivery, everyone wants it, but 
it’s ultimately stupid to not release at all before preparing a perfect 
continuous delivery pipeline.

I just want to set some version number in my POM and be sure that everyone else 
will build it with the exactly same JAR, not something around one day and 2 
years old. Damn, this is the main purpose of versioning. Is that so big 
problem?!

I can’t believe that I have to argue about such an elementary thing with 
author of the testing framework…

Original comment by ja...@jirutka.cz on 12 Dec 2014 at 1:27

[GoogleCodeExporter]

Previous releases took about a day of work. If you don't want to use something 
that's 2 years old and works perfectly fine, you'll have to wait for the next 
release.

Original comment by pnied...@gmail.com on 12 Dec 2014 at 1:38

[GoogleCodeExporter]

How long? One year? Ten years…? Two years are like eternity in ICT.

Could you *please* write what *exactly* should be done so we can help you with 
it? I really don’t know where’s the problem. I do publish artefacts to 
Maven Central and maybe I’m doing something terribly wrong, but I don’t see 
it as a huge problem. Once again, it may not be a perfect release with perfect 
changelog, precisely updated documentation etc.

Original comment by ja...@jirutka.cz on 12 Dec 2014 at 1:53

[GoogleCodeExporter]

Original comment by pnied...@gmail.com on 3 Mar 2015 at 2:45

• Changed state: Fixed
• Added labels: Milestone-1.0