4.1 release tasks

>Folks -
>
>As stated in the previous message, here is a thread to gather release tasks and the time frame in which they should be addressed. I'm taking the "4 weeks to release" rather literally below because I want to avoid excessive discussions about what we should do with feature x or y. Rather, I'm saying let's ship it as it is, get it out quickly, and spend our time moving forward from there. With that said, here we go:
>
>[ ] Build a 4.1alpha trunk image
>What: We need to re-apply all the changes that went into trunk on top of 4.0 to create a proper 4.1 alpha. I'm planning to do this by the weekend and remove the previous trunk images since they're now obsolete.
>Who: Andreas
>When: March 20th
>
>[ ] Feature Freeze trunk
>What: Feature freeze the trunk. Only fixes for identified issues go in.
>Who: All core-devs.
>When: March 28th
>
>(this gives us one more week if you have anything that you feel strongly about)
>
>[ ] Make tests green
>What: Review all the tests on all platform; identify failing tests, make them pass or document known failures.
>Who: ???
>When: April 4th (this is a bit of wishful thinking...)
>
>[ ] Ensure current VMs
>What: Ensure that all platforms have current VMs available, with all required fixes applied.
>Who: VM maintainers
>When: April 4th
>
>[ ] Create a 4.1 release repository on source.squeak.org
>What: Create a release repository that we can point the release image to for subsequent 4.1 maintenance updates.
>Who: Any source.squeak.org admin
>When: ASAP.
>
>[ ] Identify Mantis bugs that should be in 4.1
>What: Categorize bugs that need to be looked at for the 4.1 release (does NOT imply fixing the bugs)
>Who: Everyone.
>When: April 4th.
>
>[ ] Build release candidates
>What: Start building release candidates to ensure we have a process. Casey probably still has a few make files around.
>Who: ???
>When: Ongoing.
>
>[ ] Write welcome message, press release
>What: Write a welcome message, overview of changes, press release etc.
>Who: ???
>When: April 4th.
>
>As a time line we get:
>
>ASAP:
>- Create 4.1 release repository
>
>March 20th:
>- Build a 4.1alpha trunk image
>
>March 28th:
>- Feature Freeze
>- RC1 build
>
>April 4th:
>- Green tests
>- Updated VMs
>- Mantis bugs organized
>- Welcome message, press release
>- RC2 build
>
>April 11th:
>- All bugs fixed (yeah, right :-)
>- RC3 build
>
>April 17th:
>- Ship date
>
>This is obviously a tight schedule but if we want to get the puppy out in four weeks we need to get schtuff done. I don't think it's unreasonable though; all the tasks are doable on their own, we just need a few people to step up and pick one they can help with.
>
>Cheers,
>  - Andreas

> I think this deserves to be documented as a proposal, as is the normal requirement by the SOB and placed somewhere officially as a permanent record.
> When this proposal has been accepted by the SOB this should be noted there as well.
>
> Ken G. Brown
>
> At 8:28 PM -0700 3/17/10, Andreas Raab apparently wrote:
>>Folks -
>>
>>As stated in the previous message, here is a thread to gather release tasks and the time frame in which they should be addressed. I'm taking the "4 weeks to release" rather literally below because I want to avoid excessive discussions about what we should do with feature x or y. Rather, I'm saying let's ship it as it is, get it out quickly, and spend our time moving forward from there. With that said, here we go:
>>
>>[ ] Build a 4.1alpha trunk image
>>What: We need to re-apply all the changes that went into trunk on top of 4.0 to create a proper 4.1 alpha. I'm planning to do this by the weekend and remove the previous trunk images since they're now obsolete.
>>Who: Andreas
>>When: March 20th
>>
>>[ ] Feature Freeze trunk
>>What: Feature freeze the trunk. Only fixes for identified issues go in.
>>Who: All core-devs.
>>When: March 28th
>>
>>(this gives us one more week if you have anything that you feel strongly about)
>>
>>[ ] Make tests green
>>What: Review all the tests on all platform; identify failing tests, make them pass or document known failures.
>>Who: ???
>>When: April 4th (this is a bit of wishful thinking...)
>>
>>[ ] Ensure current VMs
>>What: Ensure that all platforms have current VMs available, with all required fixes applied.
>>Who: VM maintainers
>>When: April 4th
>>
>>[ ] Create a 4.1 release repository on source.squeak.org
>>What: Create a release repository that we can point the release image to for subsequent 4.1 maintenance updates.
>>Who: Any source.squeak.org admin
>>When: ASAP.
>>
>>[ ] Identify Mantis bugs that should be in 4.1
>>What: Categorize bugs that need to be looked at for the 4.1 release (does NOT imply fixing the bugs)
>>Who: Everyone.
>>When: April 4th.
>>
>>[ ] Build release candidates
>>What: Start building release candidates to ensure we have a process. Casey probably still has a few make files around.
>>Who: ???
>>When: Ongoing.
>>
>>[ ] Write welcome message, press release
>>What: Write a welcome message, overview of changes, press release etc.
>>Who: ???
>>When: April 4th.
>>
>>As a time line we get:
>>
>>ASAP:
>>- Create 4.1 release repository
>>
>>March 20th:
>>- Build a 4.1alpha trunk image
>>
>>March 28th:
>>- Feature Freeze
>>- RC1 build
>>
>>April 4th:
>>- Green tests
>>- Updated VMs
>>- Mantis bugs organized
>>- Welcome message, press release
>>- RC2 build
>>
>>April 11th:
>>- All bugs fixed (yeah, right :-)
>>- RC3 build
>>
>>April 17th:
>>- Ship date
>>
>>This is obviously a tight schedule but if we want to get the puppy out in four weeks we need to get schtuff done. I don't think it's unreasonable though; all the tasks are doable on their own, we just need a few people to step up and pick one they can help with.
>>
>>Cheers,
>>  - Andreas
>
>
>

>On 19.03.2010, at 02:31, Ken G. Brown wrote:
>>
>> I think this deserves to be documented as a proposal, as is the normal requirement by the SOB
>
>OMG. How about you actually *contribute* something to the release instead of wallowing in procedural motions?
>
>The election has clearly shown that the informal way we operate is generally fine with the community. Every member of the SOB who decided to run was re-elected.
>
>That's not to say we couldn't establish some formalities but for now as you well know there is no "normal requirement" for anything.
>
>So, please grab a coffee and test the current trunk image. Add issues to the blocker ticket Alex opened. Or make some test green. Or start writing a nice readme. Or outline a press release. Or indeed anything non-meta, please?
>
>Have fun.
>
>- Bert -

> At 10:24 AM +0100 3/19/10, Bert Freudenberg apparently wrote:
>> On 19.03.2010, at 02:31, Ken G. Brown wrote:
>>>
>>> I think this deserves to be documented as a proposal, as is the normal requirement by the SOB
>>
>> OMG. How about you actually *contribute* something to the release instead of wallowing in procedural motions?
>>
>> The election has clearly shown that the informal way we operate is generally fine with the community. Every member of the SOB who decided to run was re-elected.
>>
>> That's not to say we couldn't establish some formalities but for now as you well know there is no "normal requirement" for anything.
>>
>> So, please grab a coffee and test the current trunk image. Add issues to the blocker ticket Alex opened. Or make some test green. Or start writing a nice readme. Or outline a press release. Or indeed anything non-meta, please?
>>
>> Have fun.
>>
>> - Bert -
>
> Ok, I've set up a simple blog to help the SOB out.
>
> SQUEAK OVERSIGHT BOARD
> THE SQUEAK OVERSIGHT BOARD (SOB) GENERAL FAQ, GUIDELINES AND OPERATING PROCEDURES
> <http://squeakoversightboard.blogspot.com/>
>
> It has an associated email <[hidden email]> which I needed in order to create the blog. The email could be set to forward to the SOB members or where ever you would like, although it is not listed on the bog for now. I did not want to post that unless you want to start using it.
>
> I edited email addresses in order to obscure, on the emails I forwarded to the blog as posts since this will be publicly available. Let me know if I've missed any, or if in fact the email addresses should perhaps be left intact, I was unsure what people would like in this case.
>
> If any SOB members would like direct posting access let me know, and I can give you the 'secret' email address for posting, just send an email and the subject becomes the post title, and the message body gets automatically posted at the top. They can be edited afterwards too of course.
>
> For now I've just posted some items that have recently appeared here that would help people to understand how the SOB operates.
>
> If there is anything else that should be added, please let me know. Blogspot blogs are pretty flexible and easy to use. Lot's of features can be enabled but for now I just wanted to get this out for everyone to have a look at.
>
> Ken G. Brown
>
>

>
> At 10:24 AM +0100 3/19/10, Bert Freudenberg apparently wrote:
>> On 19.03.2010, at 02:31, Ken G. Brown wrote:
>>>
>>> I think this deserves to be documented as a proposal, as is the normal requirement by the SOB
>>
>> OMG. How about you actually *contribute* something to the release instead of wallowing in procedural motions?
>>
>> The election has clearly shown that the informal way we operate is generally fine with the community. Every member of the SOB who decided to run was re-elected.
>>
>> That's not to say we couldn't establish some formalities but for now as you well know there is no "normal requirement" for anything.
>>
>> So, please grab a coffee and test the current trunk image. Add issues to the blocker ticket Alex opened. Or make some test green. Or start writing a nice readme. Or outline a press release. Or indeed anything non-meta, please?
>>
>> Have fun.
>>
>> - Bert -
>
> Ok, I've set up a simple blog to help the SOB out.
>
> SQUEAK OVERSIGHT BOARD
> THE SQUEAK OVERSIGHT BOARD (SOB) GENERAL FAQ, GUIDELINES AND OPERATING PROCEDURES
> <http://squeakoversightboard.blogspot.com/>

>On Fri, 19 Mar 2010, Ken G. Brown wrote:
>
>>At 10:24 AM +0100 3/19/10, Bert Freudenberg apparently wrote:
>>>On 19.03.2010, at 02:31, Ken G. Brown wrote:
>>>>
>>>>I think this deserves to be documented as a proposal, as is the normal requirement by the SOB
>>>
>>>OMG. How about you actually *contribute* something to the release instead of wallowing in procedural motions?
>>>
>>>The election has clearly shown that the informal way we operate is generally fine with the community. Every member of the SOB who decided to run was re-elected.
>>>
>>>That's not to say we couldn't establish some formalities but for now as you well know there is no "normal requirement" for anything.
>>>
>>>So, please grab a coffee and test the current trunk image. Add issues to the blocker ticket Alex opened. Or make some test green. Or start writing a nice readme. Or outline a press release. Or indeed anything non-meta, please?
>>>
>>>Have fun.
>>>
>>>- Bert -
>>
>>Ok, I've set up a simple blog to help the SOB out.
>>
>>SQUEAK OVERSIGHT BOARD
>>THE SQUEAK OVERSIGHT BOARD (SOB) GENERAL FAQ, GUIDELINES AND OPERATING PROCEDURES
>><http://squeakoversightboard.blogspot.com/>
>>
>>It has an associated email <[hidden email]> which I needed in order to create the blog. The email could be set to forward to the SOB members or where ever you would like, although it is not listed on the bog for now. I did not want to post that unless you want to start using it.
>>
>>I edited email addresses in order to obscure, on the emails I forwarded to the blog as posts since this will be publicly available. Let me know if I've missed any, or if in fact the email addresses should perhaps be left intact, I was unsure what people would like in this case.
>>
>>If any SOB members would like direct posting access let me know, and I can give you the 'secret' email address for posting, just send an email and the subject becomes the post title, and the message body gets automatically posted at the top. They can be edited afterwards too of course.
>>
>>For now I've just posted some items that have recently appeared here that would help people to understand how the SOB operates.
>>
>>If there is anything else that should be added, please let me know. Blogspot blogs are pretty flexible and easy to use. Lot's of features can be enabled but for now I just wanted to get this out for everyone to have a look at.
>>
>>Ken G. Brown
>>
>
>What's the point? Confusing people?
>The SOB already has a blog: http://squeakboard.wordpress.com/
>
>
>Levente

> >>>>> "Ken" == Ken G Brown <[hidden email]> writes:
>
>Ken> Ok, I've set up a simple blog to help the SOB out.
>
>I consider this a hostile act.  You seem to presume this will help the SOB.
>It will not.  The SOB has a blog, and communicates both there and here, and
>answered your questions as you asked them.
>
>You have now enabled the "ignore him, he's a kook" bit for me, as well as
>probably any other rational thinker on this list.  Good luck with that.
>
>--
>Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
><[hidden email]> <URL:http://www.stonehenge.com/merlyn/>
>Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
>See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion

>On 2010-03-19, at 9:37 AM, Ken G. Brown wrote:
>
>> Ok, I've set up a simple blog to help the SOB out.
>>
>> SQUEAK OVERSIGHT BOARD
>> THE SQUEAK OVERSIGHT BOARD (SOB) GENERAL FAQ, GUIDELINES AND OPERATING PROCEDURES
>> <http://squeakoversightboard.blogspot.com/>
>
>Wow. I can't think of any situation in which speaking on behalf of someone else, without their permission, would be OK. Ken, how would you feel if I created a blog called kengbrown.blogspot.com and started posting stuff you didn't agree with?
>
>Colin

> At 10:55 AM -0700 3/19/10, Colin Putney apparently wrote:
>>On 2010-03-19, at 9:37 AM, Ken G. Brown wrote:
>>
>>> Ok, I've set up a simple blog to help the SOB out.
>>>
>>> SQUEAK OVERSIGHT BOARD
>>> THE SQUEAK OVERSIGHT BOARD (SOB) GENERAL FAQ, GUIDELINES AND OPERATING PROCEDURES
>>> <http://squeakoversightboard.blogspot.com/>
>>
>>Wow. I can't think of any situation in which speaking on behalf of someone else, without their permission, would be OK. Ken, how would you feel if I created a blog called kengbrown.blogspot.com and started posting stuff you didn't agree with?
>>
>>Colin
>
> I set the blog up for the SOB to use as they see fit.
> I just posted some important stuff I saw go by on the list as a start to have something there to look at.
>
> Ken G. Brown
>
>