Brian E. Fox wrote:
It's not entirely true that versions don't matter. Alpha or Beta is
really a less important distinction and we are generally trying to move
away from more alpha/beta releases. I would argue that since Maven
requires Shade to release, that the current version should be 1.0 not
alpha or beta.
Doing a release is much more than slapping a version (tag) on it. It
makes the next version usable by other people to do releases because it
means we've pushed a non-snapshot to the public. If there are people
unaffected by MSHADE-9, then there is still value to those people in
having a release now rather than later. I think in general we try to fix
too many things at once and end up not getting important fixes out to
the people that need them. I'd rather see a release come out with the
current fixes and then when MSHADE-9 is fixed, we do another release. At
least then some people can use it rather than making everyone wait...and
realistically doing the release doesn't preclude someone from fixing the
issue in parallel so it shouldn't in theory delay the inevitable release
with the MSHADE-9 fix in it.
+1
Betas (and alphas) IMO should be milestones towards a final major
release 1.x or 2.x. But all too often betas tend to get treated as
"final" releases. No problem in having a release with a known issue (in
this case MSHADE-9).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
