You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Jim Marino <jm...@myromatours.com> on 2006/05/04 21:54:01 UTC

release naming scheme

Hi,

I've noticed in JIRA we are naming our release ".91". Is that just a  
JIRA thing (i.e. make it easier to organize stuff for us) or is it  
assumed that we would call the JavaOne binary a ".91" release? I  
think we should discuss what we want to call the binary, so I'll  
throw my opinion in now...

I think we should definitely not call it a ".9X" release as that  
denotes a fairly stable runtime, which we will not have. My proposal  
is to view this as a milestone release, so perhaps we should just  
call it "M1" and avoid numbering altogether?

Thoughts?
Jim

Re: release naming scheme

Posted by Jean-Sebastien Delfino <js...@apache.org>.
Jim Marino wrote:
> Hi,
>
> I've noticed in JIRA we are naming our release ".91". Is that just a 
> JIRA thing (i.e. make it easier to organize stuff for us) or is it 
> assumed that we would call the JavaOne binary a ".91" release? I think 
> we should discuss what we want to call the binary, so I'll throw my 
> opinion in now...
>
> I think we should definitely not call it a ".9X" release as that 
> denotes a fairly stable runtime, which we will not have. My proposal 
> is to view this as a milestone release, so perhaps we should just call 
> it "M1" and avoid numbering altogether?
>
> Thoughts?
> Jim
>
Jim, I agree. I just had to come up with something to be able to 
schedule the resolution of JIRA issues. 0.91 was for JIRAs targeted for 
our  JavaOne tentative release, 0.9x a placeholder for JIRAs out of this 
release, Unscheduled for JIRAs with an undetermined target. I just 
changed 0.91 to M1 and 0.9x to Mx and can change again later if people 
have a better idea.

As of now we have 64 unresolved JIRAs in M1, 23 in Mx, 57 unscheduled.

-- 
Jean-Sebastien