On 1/30/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> As I explained in response to your previous message, we already do that.
> You fixes were scheduled for, and always have been scheduled for 2.1.

Sorry but it's not marked as such in Jira

http://jira.codehaus.org/browse/MASSEMBLY-19

Component/s:     None
Affects Version/s:      None
Fix Version/s:  None

Same for

http://jira.codehaus.org/browse/MASSEMBLY-35

> 2.1 has not been delayed in any way. 2.0.1 was pushed up with some bug
> fixes that were represented as more critical.
>
> As soon as the outstanding 2.1 bugs/features are completed, it will be
> released. If you now feel your bugfix is very critical, then it can be
> considered for backporting to the 2.0.x branch and a 2.0.2 release can
> be made. The lack of versions in JIRA back to 3 months ago limited our
> ability to do that.

To me it's critical. I initially reported it as Critical in Jira. Next
time should I make it a blocker?

I added this in the first lines of the issue description.

"[I hope this can be looked into before official 2.0 otherwise that
could create issues with regard to breaking existing code. Making
critical for this reason]"

On IRC, when I saw that it missed 2.0 I am pretty certain someone told
me that 2.0.1 would be out soon (to me implying that it would be in).

I don't know what else I could do appart from notifying you that it
wasn't included in the forthcoming release. I missed the vote mail
(which maybe shouldn't be on the dev list?).

WRT to backport, I asked in another mail thread to backport it and
make a 2.0.2. I feelt that the longer you stay with this issue in the
code, the more you have a chance to break existing user configurations
who will do the upgrade.

> As for betas of plugins - that's definitely something we'd like to do
> but we don't have the repository separation setup right now. What we ask
> people to do is test snapshots instead. Perhaps a better idea is to push
> that to the users@ list for greater notice. When we have the announce@
> list that will be different.

OK. That sounds good.

Jerome

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to