You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Kevan Miller <ke...@gmail.com> on 2010/08/20 15:25:14 UTC
2.2.x
I'm hoping we'll have things lined up for 2.2.x release in mid-September. branches/2.2 is currently 2.2.2-SNAPSHOT. As we were preparing for a minimal 2.2.1 release. Given where we are, I think we discard the thoughts of this minimal update, and change branches/2.2 back to 2.2.1-SNAPSHOT. This could cause some maven resolution issues. One way to find out, I guess. Any comments?
--kevan
Re: 2.2.x
Posted by Rick McGuire <ri...@gmail.com>.
On 8/20/2010 9:25 AM, Kevan Miller wrote:
> I'm hoping we'll have things lined up for 2.2.x release in mid-September. branches/2.2 is currently 2.2.2-SNAPSHOT. As we were preparing for a minimal 2.2.1 release. Given where we are, I think we discard the thoughts of this minimal update, and change branches/2.2 back to 2.2.1-SNAPSHOT. This could cause some maven resolution issues. One way to find out, I guess. Any comments?
I think at this point the blockers to releasing the minimal 2.2.1
release and the 2.2.2 release are essentially the same. I think
scrapping the current 2.2.1 branch and rolling the branches/2.2 back to
2.2.1-SNAPSHOT makes a lot of sense. I'm not aware of any maven
resolution issues this will created, but maven can be a constant source
of surprise. It might not be a bad idea to delete all of the 2.2.1 and
2.2.2 artifacts from the apache snapshot repository before committing
these changes.
Rick
> --kevan
Re: 2.2.x
Posted by Ivan <xh...@gmail.com>.
If we could resolve the maven issue easily, I am +1 for changing the branch
to 2.2.1-SNAPSHOT. Or I guess that we will be always asked where is 2.2.1 in
the future :-)
2010/8/20 Kevan Miller <ke...@gmail.com>
> I'm hoping we'll have things lined up for 2.2.x release in mid-September.
> branches/2.2 is currently 2.2.2-SNAPSHOT. As we were preparing for a minimal
> 2.2.1 release. Given where we are, I think we discard the thoughts of this
> minimal update, and change branches/2.2 back to 2.2.1-SNAPSHOT. This could
> cause some maven resolution issues. One way to find out, I guess. Any
> comments?
>
> --kevan
--
Ivan