You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Matt Hogstrom <ma...@hogstrom.org> on 2007/02/26 15:18:04 UTC

2.0-M3 - Building the release later today

Are there any outstanding issues with the branch that need to be  
resolved that anyone is aware of?  If not I'll cut the release for a  
vote this evening.

Re: 2.0-M3 - Building the release later today

Posted by Jason Dillon <ja...@planet57.com>.
You might just rename 2.0-beta1 to 2.0-M3, then create a new 2.0- 
beta1...

--jason


On Feb 26, 2007, at 2:59 PM, Matt Hogstrom wrote:

> Ya, I'll remap the ones closed against beta-1 to M3 and close  
> M2...thanks.
>
> On Feb 26, 2007, at 4:50 PM, Jason Dillon wrote:
>
>> Matt, when you release m3 today... what JIRA version does that map  
>> to?  Looks like some of the issues were for 2.0-beta-1, which  
>> appears to be what 2.0-m3 is.  It would be swell if you could keep  
>> the JIRA version's in sync with reality.
>>
>> And along those lines be sure to mark 2.0-m2 as released with what  
>> ever date it went out on... and do the same for 2.0-m3.  This is  
>> important to keep the JIRA roadmap/changelog feature functional.
>>
>> --jason
>>
>>
>> On Feb 26, 2007, at 6:18 AM, Matt Hogstrom wrote:
>>
>>> Are there any outstanding issues with the branch that need to be  
>>> resolved that anyone is aware of?  If not I'll cut the release  
>>> for a vote this evening.
>>
>>
>


Re: 2.0-M3 - Building the release later today

Posted by Matt Hogstrom <ma...@hogstrom.org>.
Ya, I'll remap the ones closed against beta-1 to M3 and close  
M2...thanks.

On Feb 26, 2007, at 4:50 PM, Jason Dillon wrote:

> Matt, when you release m3 today... what JIRA version does that map  
> to?  Looks like some of the issues were for 2.0-beta-1, which  
> appears to be what 2.0-m3 is.  It would be swell if you could keep  
> the JIRA version's in sync with reality.
>
> And along those lines be sure to mark 2.0-m2 as released with what  
> ever date it went out on... and do the same for 2.0-m3.  This is  
> important to keep the JIRA roadmap/changelog feature functional.
>
> --jason
>
>
> On Feb 26, 2007, at 6:18 AM, Matt Hogstrom wrote:
>
>> Are there any outstanding issues with the branch that need to be  
>> resolved that anyone is aware of?  If not I'll cut the release for  
>> a vote this evening.
>
>


Re: 2.0-M3 - Building the release later today

Posted by Jason Dillon <ja...@planet57.com>.
Matt, when you release m3 today... what JIRA version does that map  
to?  Looks like some of the issues were for 2.0-beta-1, which appears  
to be what 2.0-m3 is.  It would be swell if you could keep the JIRA  
version's in sync with reality.

And along those lines be sure to mark 2.0-m2 as released with what  
ever date it went out on... and do the same for 2.0-m3.  This is  
important to keep the JIRA roadmap/changelog feature functional.

--jason


On Feb 26, 2007, at 6:18 AM, Matt Hogstrom wrote:

> Are there any outstanding issues with the branch that need to be  
> resolved that anyone is aware of?  If not I'll cut the release for  
> a vote this evening.