On 1/27/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > see below > > On 1/27/06, jerome lacoste <[EMAIL PROTECTED]> wrote: > > On 1/27/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > > > As I said in the vote only three bugfixes were into 2.0.1 to make it > > > more stable and prevent new funtionality that could bring new bugs. > > > > My bad for not reading your original mail. I was particularly > > surprised, in particular because of MASSEMBLY-19. It was a one line > > fix, that I reported as critical. Surprisingly it wasn't considered > > for 2.0 and I didn't expect it to miss 2.0.1. > > > I took 2.0 code and made a branch fixed the issues I needed at the > moment. I expected that if somebody would like to have another bug > fixed would talk during the vote > [...]
> I think it's a good idea if you want other bug fixes, to apply them to > the 2.0.x branch and update jira with the fix version. We can call a > vote for 2.0.2 after. I will come back to the process issues in another thread, because I still think there something to do there. But in the mean time the latest stable assembly is broken for me (it doesn't work on multi-projects). So I would recommend a new release ASAP, with at least MASSEMBLY-19 in it. The patch is a one liner, so it should apply as is on the branch. And there's not much I can do to make this happen. So it's up to you guys. Feel free to add other fixes. Let me know is this is going to happen or not and if this is going to take 72 hours as well :) Jerome --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
