making a release doesn't mean that things can't change in the future,
the more stuff we try to throw in a release the longer users will wait
and the more more problems to track bugs/problems. If we do 0.9 and
1.0 or whatever numbers then it'll be easier to know if the bug is in
the previous code or in the new one.
On 4/10/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 4/10/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
> Also, the work that is identified by MRM-153 + 211 + 212 are moot in the
> branch, as other, more fundamental solutions has been worked out for
> dealing with remote repositories, checksum policy, and maven 1 clients.
...
> Any release of trunk should be considered pre-1.0 (not even alpha-1) as
> it is so broken.
Thanks for the detailed list of issues. And I edited out a suggestion
to release it as 0.9 and leave the 1.0 version for the work on the
branch, so let's go with that, assuming...
Arnaud, Nicolas, are you planning to work on trunk and get the fixes
in there, or are you content to wait on the branch?
--
Wendy
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
