On 31 December 2012 14:12, Nicolas Cellier
<nicolas.cellier.aka.nice at gmail.com> wrote:
> 2012/12/31 Frank Shearar <frank.shearar at gmail.com>:
>> On 31 December 2012 14:03, Nicolas Cellier
>> <nicolas.cellier.aka.nice at gmail.com> wrote:
>>> I noticed the copyright stops at 2011, it should be at least 2012 (if
>>> you're fast enough...)
>>
>> Where does that appear?
>>
>> frank
>>
>
> The  "Licence" workspace

Thanks! System-fbs.506 contains the fix. And I beat the
ReleaseSqueakTrunk job into submission:
http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/target/Squeak4.4-12326.zip

I'd really like to release this guy today, so if anyone has anything
_urgent_ to get in, now's the time.

I still have to do two more things for this release: populate the 44
update stream, and then declare 4.4 finished. I don't think we need to
do anything further to make trunk ready for 4.5, do we? 4.5 alpha just
becomes the update after 4.4 splits off.

Regarding the All-in-One, is it sufficient to take the 4.3 one and
replace the Cog and image/changes file in it to produce a new one?

frank

>>> Nicolas
>>>
>>> 2012/12/31 Frank Shearar <frank.shearar at gmail.com>:
>>>> On 29 December 2012 22:15, Frank Shearar <frank.shearar at gmail.com> wrote:
>>>>> On 29 December 2012 21:06, Frank Shearar <frank.shearar at gmail.com> wrote:
>>>>>> On 29 December 2012 18:49, Levente Uzonyi <leves at elte.hu> wrote:
>>>>>>> On Sat, 29 Dec 2012, Frank Shearar wrote:
>>>>>>>
>>>>>>>> Other than the fact that the last two builds for SqueakTrunk have hung
>>>>>>>> - an issue I'm looking into, but wouldn't mind others trying their
>>>>>>>> luck - are we happy enough with 4.4 that we'd want to ship it?
>>>>>>>>
>>>>>>>> My gut feel is (and with my Release Manager hat on), judging by the
>>>>>>>> low severity of the few reports we're seeing, that we're there. What
>>>>>>>> do others think?
>>>>>>>>
>>>>>>>
>>>>>>> I think it's time to release it, even though SqueakSSL doesn't like the
>>>>>>> network changes.
>>>>>>
>>>>>> OK. Once I uncover whatever's hanging the SqueakTrunk build I'll yell,
>>>>>> and we can give the ReleaseSqueakTrunk artifact one more whirl and
>>>>>> declare victory.
>>>>>
>>>>> It MAY be that there was an intermittent issue with source.squeak.org
>>>>> not accepting connections: I saw a ConnectionRefused while trying to
>>>>> reproduce the hung build locally. That could be because of my flakey
>>>>> home wifi, but then again (a) such an exception would raise a debugger
>>>>> and hang the build and (b) the builds have started not hanging [1]. At
>>>>> any rate, they do log a lot more: the update number, the tests they're
>>>>> running, and so on.
>>>>
>>>> SqueakTrunk looks like it's back in business. ReleaseSqueakTrunk still
>>>> has issues, because it looks like it's confused (or I've confused it)
>>>> as to the artifacts it's supposed to use: it's consistently releasing
>>>> 12324-based images instead of 12326-based ones. I shall hack on...
>>>>
>>>> frank
>>>>
>>>>> [1] http://squeakci.org/job/SqueakTrunk/83/console
>>>>>
>>>>>> frank
>>>>>>
>>>>>>> Levente
>>>>>>>
>>>>>>>
>>>>>>>> One thing we _don't_ have is an "All-in-one" one-click type installer
>>>>>>>> for the various OSes. If someone can show me what to do, I can add a
>>>>>>>> job to spit out such a thing.
>>>>>>>>
>>>>>>>> frank
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>
>>>
>>
>