KR,
And that's pretty much what I was saying as far as releasing early and
often. While everyone can do what Freddy did/does doesn't it make more
sense to work with a release snapshot albeit beta or whatever.
Honestly - if anyone - new or old - to stripes were to choose between:
1) Door #1
- Checking out what may or may not be stable code from a trunk
- Pull together its dependencies
- Compile and package my own jar
- Upload it to my local version repository
- Update Stripes version in my project's M2 pom and
- Re-build my M2 project
-- VS. --
2) Door #2
- Update Stripes version in my project's M2 pom and
- Re-build my M2 project
What door do we expect - new or old - Stripes Developers to pick?
And not to say that I haven't elected Door #1 over the years w.r.t.
OTHER products - I have - MOST of the time b/c I had no other choice but
to do so to get a fix I desperately needed... however of the times I
choose to do so b/c I wanted to work / play with the latest I too have
been burnt before by not timing the "its stable today" extraction and
having all sorts of issues and simply having to fall back to a working
stable release with only lost time and grief to show for it.
So to re-iterate KR's sentiment:
If 1.6 is stable, why don't label a stable version "beta 1"?
Surely releasing a beta is a good thing... NO?
--Nikolaos
KR wrote:
If 1.6 is stable, why don't label a stable version "beta 1"?
"Freddy Daoud" <[email protected]> wrote in message
news:[email protected]...
I should have been more specific:
Case in point today the trunk is fine and quite "usable" as you put it
but tomorrow after some "next commit" it might not be the case...
I agree. What I did was take a snapshot of the trunk and called
it 1.6-SNAPSHOT, but I don't update it at every commit. I put
it in a Maven repo and just use that in my projects. I won't
update it unless something happens in the trunk that I need.
Like I said, this isn't for everyone. But for my purposes, it
fits the bill.
Cheers,
Freddy
------------------------------------------------------------------------------
------------------------------------------------------------------------------
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
