Hi, Just back from vacation, see a blizzard of JIRA activity. Go, Henning!
I think we should do a release, but do not think we should call it Release Candidate / RC. To me, a RC is ready to go, no open bugs, no missing docs. We're close but not there. Let's do a release and call it a "beta". We had a discussion about doing this a long time ago. Maybe set a date for final tweaks, i.e. Friday the 15th? Could provide a little incentive to commit VELOCITY-422 (has patch), VELOCITY-453 (has patch, needs tweak), VELOCITY-132 (has patch, needs tweak). So, -1 to RC. But a counter proposal of "Velocity 1.5-beta" occurring shortly after 9/15. WILL On 9/5/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
Just do an RC, and then add more things, and then do 1.6... Just do it. geir Henning P. Schmiedehausen wrote: > Hi, > > as we are dragging the 1.5 release out: How about cutting an RC? A version > that is basically "code complete but some docs missing". Are there any > pending JIRA issues that absolutely should be in? > > [ ] +1 RC is cool. > [ ] 0 I don't care. > [ ] -1 No we still have show stoppers (please elaborate). > > I'll collect votes till thursday. > > Best regards > Henning > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
