Re: [VOTE] 1.1 Code Freeze to start Monday 0600 PT - Ship 1.1 on Cinco De Mayo
Let's plan on a 1.1-beta some time between May 1 and May 8 if we think most of the functional errors are fixed, then a 1.1-rc as soon as we're comfortable with any fixes to the beta and we think all the softer things like documentation and stuff are fixed, and then a 1.1 as soon after that as possible. I'd be fine if we don't publicize the "beta" but just use that as a milestone to the RC (and to work out the issues around making sure there aren't dangling SNAPSHOT references in our source and so on). I definitely want to release no later than JavaOne, but earlier would be totally fine with me if the stability is there and the docs have caught up (so we won't be confusing people with the 1.0/1.1 syntax differences, etc.). Thanks, Aaron On 4/21/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote: > +1 > > and I agree with Aaron about being flexible about ship date > > Any interest in releasing/announcing at JavaOne? > > geir > > > Matt Hogstrom wrote: > > All, > > > > I'd like to propose we close 1.1 and start putting the wrapping tape on > > the box. There have been new features / functions coming in and at some > > point we need to collectively get this one out the door and focus on > > 1.2. So here is the vote to agree to close features and focus on bugs / > > JIRAs so we can complete this one. > > > > [ ] +1 - Close development for 1.1 on Monday 4/24 0600 PT > > [ ] 0 - No preference > > [ ] -1 - Let's cram as much in as we can > > > > Of course this doesn't mean that we don't fix bugs. > > > > Matt > > > > >
Re: [VOTE] 1.1 Code Freeze to start Monday 0600 PT - Ship 1.1 on Cinco De Mayo
+1 and I agree with Aaron about being flexible about ship date Any interest in releasing/announcing at JavaOne? geir Matt Hogstrom wrote: All, I'd like to propose we close 1.1 and start putting the wrapping tape on the box. There have been new features / functions coming in and at some point we need to collectively get this one out the door and focus on 1.2. So here is the vote to agree to close features and focus on bugs / JIRAs so we can complete this one. [ ] +1 - Close development for 1.1 on Monday 4/24 0600 PT [ ] 0 - No preference [ ] -1 - Let's cram as much in as we can Of course this doesn't mean that we don't fix bugs. Matt
Re: [VOTE] 1.1 Code Freeze to start Monday 0600 PT - Ship 1.1 on Cinco De Mayo
[X] +1 - Close development for 1.1 on Monday 4/24 0600 PT Cheers! Hernan Matt Hogstrom wrote: All, I'd like to propose we close 1.1 and start putting the wrapping tape on the box. There have been new features / functions coming in and at some point we need to collectively get this one out the door and focus on 1.2. So here is the vote to agree to close features and focus on bugs / JIRAs so we can complete this one. [ ] +1 - Close development for 1.1 on Monday 4/24 0600 PT [ ] 0 - No preference [ ] -1 - Let's cram as much in as we can Of course this doesn't mean that we don't fix bugs. Matt
Re: [VOTE] 1.1 Code Freeze to start Monday 0600 PT - Ship 1.1 on Cinco De Mayo
+1 On 4/20/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > All, > > I'd like to propose we close 1.1 and start putting the wrapping tape on the > box. There have been > new features / functions coming in and at some point we need to collectively > get this one out the > door and focus on 1.2. So here is the vote to agree to close features and > focus on bugs / JIRAs so > we can complete this one. > > [ ] +1 - Close development for 1.1 on Monday 4/24 0600 PT > [ ] 0 - No preference > [ ] -1 - Let's cram as much in as we can > > Of course this doesn't mean that we don't fix bugs. > > Matt > -- James --- http://radio.weblogs.com/0112098/
Re: [VOTE] 1.1 Code Freeze to start Monday 0600 PT - Ship 1.1 on Cinco De Mayo
+1 - sachin On Apr 20, 2006, at 4:45 PM, Matt Hogstrom wrote: All, I'd like to propose we close 1.1 and start putting the wrapping tape on the box. There have been new features / functions coming in and at some point we need to collectively get this one out the door and focus on 1.2. So here is the vote to agree to close features and focus on bugs / JIRAs so we can complete this one. [ ] +1 - Close development for 1.1 on Monday 4/24 0600 PT [ ] 0 - No preference [ ] -1 - Let's cram as much in as we can Of course this doesn't mean that we don't fix bugs. Matt
Re: [VOTE] 1.1 Code Freeze to start Monday 0600 PT - Ship 1.1 on Cinco De Mayo
[X] +1 - Close development for 1.1 on Monday 4/24 0600 PT Matt Hogstrom wrote: All, I'd like to propose we close 1.1 and start putting the wrapping tape on the box. There have been new features / functions coming in and at some point we need to collectively get this one out the door and focus on 1.2. So here is the vote to agree to close features and focus on bugs / JIRAs so we can complete this one. [ ] +1 - Close development for 1.1 on Monday 4/24 0600 PT [ ] 0 - No preference [ ] -1 - Let's cram as much in as we can Of course this doesn't mean that we don't fix bugs. Matt
Re: [VOTE] 1.1 Code Freeze to start Monday 0600 PT - Ship 1.1 on Cinco De Mayo
On 4/21/06, Alan D. Cabrera <[EMAIL PROTECTED]> wrote: > But then the only real vote that counts is Aaron "I really need this > feature" Mulder's. ;) Aww, you know you'll thank me when the release notes come out. :) Thanks, Aaron > Matt Hogstrom wrote: > > All, > > > > I'd like to propose we close 1.1 and start putting the wrapping tape > > on the box. There have been new features / functions coming in and at > > some point we need to collectively get this one out the door and focus > > on 1.2. So here is the vote to agree to close features and focus on > > bugs / JIRAs so we can complete this one. > > > > [ ] +1 - Close development for 1.1 on Monday 4/24 0600 PT > > [ ] 0 - No preference > > [ ] -1 - Let's cram as much in as we can > > > > Of course this doesn't mean that we don't fix bugs. > > > > Matt > >
Re: [VOTE] 1.1 Code Freeze to start Monday 0600 PT - Ship 1.1 on Cinco De Mayo
+1 But then the only real vote that counts is Aaron "I really need this feature" Mulder's. ;) Regards, Alan Matt Hogstrom wrote: All, I'd like to propose we close 1.1 and start putting the wrapping tape on the box. There have been new features / functions coming in and at some point we need to collectively get this one out the door and focus on 1.2. So here is the vote to agree to close features and focus on bugs / JIRAs so we can complete this one. [ ] +1 - Close development for 1.1 on Monday 4/24 0600 PT [ ] 0 - No preference [ ] -1 - Let's cram as much in as we can Of course this doesn't mean that we don't fix bugs. Matt
Re: [VOTE] 1.1 Code Freeze to start Monday 0600 PT - Ship 1.1 on Cinco De Mayo
+1 --jason On Apr 20, 2006, at 1:45 PM, Matt Hogstrom wrote: All, I'd like to propose we close 1.1 and start putting the wrapping tape on the box. There have been new features / functions coming in and at some point we need to collectively get this one out the door and focus on 1.2. So here is the vote to agree to close features and focus on bugs / JIRAs so we can complete this one. [ ] +1 - Close development for 1.1 on Monday 4/24 0600 PT [ ] 0 - No preference [ ] -1 - Let's cram as much in as we can Of course this doesn't mean that we don't fix bugs. Matt
Re: [VOTE] 1.1 Code Freeze to start Monday 0600 PT - Ship 1.1 on Cinco De Mayo
[X ] +1 - Close development for 1.1 on Monday 4/24 0600 PT --kevan On Apr 20, 2006, at 4:45 PM, Matt Hogstrom wrote: All, I'd like to propose we close 1.1 and start putting the wrapping tape on the box. There have been new features / functions coming in and at some point we need to collectively get this one out the door and focus on 1.2. So here is the vote to agree to close features and focus on bugs / JIRAs so we can complete this one. [ ] +1 - Close development for 1.1 on Monday 4/24 0600 PT [ ] 0 - No preference [ ] -1 - Let's cram as much in as we can Of course this doesn't mean that we don't fix bugs. Matt
Re: [VOTE] 1.1 Code Freeze to start Monday 0600 PT - Ship 1.1 on Cinco De Mayo
[X] +1 - Close development for 1.1 on Monday 4/24 0600 PT Matt Hogstrom wrote: All, I'd like to propose we close 1.1 and start putting the wrapping tape on the box. There have been new features / functions coming in and at some point we need to collectively get this one out the door and focus on 1.2. So here is the vote to agree to close features and focus on bugs / JIRAs so we can complete this one. [ ] +1 - Close development for 1.1 on Monday 4/24 0600 PT [ ] 0 - No preference [ ] -1 - Let's cram as much in as we can Of course this doesn't mean that we don't fix bugs. Matt
Re: [VOTE] 1.1 Code Freeze to start Monday 0600 PT - Ship 1.1 on Cinco De Mayo
[X] +1 - Close development for 1.1 on Monday 4/24 0600 PT But I'm not sure about Cinco de Mayo. The last couple weeks have been REALLY rough. I'd rather have at least a week of working with 1.1 with no "oh, [EMAIL PROTECTED]" moments before we ship. Thanks, Aaron On 4/20/06, Jeff Genender <[EMAIL PROTECTED]> wrote: > [X] +1 - Close development for 1.1 on Monday 4/24 0600 PT > > Matt Hogstrom wrote: > > All, > > > > I'd like to propose we close 1.1 and start putting the wrapping tape on > > the box. There have been new features / functions coming in and at some > > point we need to collectively get this one out the door and focus on > > 1.2. So here is the vote to agree to close features and focus on bugs / > > JIRAs so we can complete this one. > > > > [ ] +1 - Close development for 1.1 on Monday 4/24 0600 PT > > [ ] 0 - No preference > > [ ] -1 - Let's cram as much in as we can > > > > Of course this doesn't mean that we don't fix bugs. > > > > Matt >
Re: [VOTE] 1.1 Code Freeze to start Monday 0600 PT - Ship 1.1 on Cinco De Mayo
[X] +1 - Close development for 1.1 on Monday 4/24 0600 PT Matt Hogstrom wrote: > All, > > I'd like to propose we close 1.1 and start putting the wrapping tape on > the box. There have been new features / functions coming in and at some > point we need to collectively get this one out the door and focus on > 1.2. So here is the vote to agree to close features and focus on bugs / > JIRAs so we can complete this one. > > [ ] +1 - Close development for 1.1 on Monday 4/24 0600 PT > [ ] 0 - No preference > [ ] -1 - Let's cram as much in as we can > > Of course this doesn't mean that we don't fix bugs. > > Matt
