[M3devel] HEADS UP: release engineering procedure clarification

[Jay K]

I'll give up on SOLgnu now building with /usr/sfw/bin/gcc, since it failed again.
   There is another experiment to try -- -with-as=/usr/sfw/bin/as -with-gnu-as.
I've changed hudson's .profile back to have /usr/local/bin in front and trying again.
It looks like release and lastok are mixed up, ok.
 
 
 - Jay


----------------------------------------
> Date: Sun, 2 Aug 2009 15:36:29 +0200
> From: wagner at elegosoft.com
> To: jay.krell at cornell.edu
> CC: m3devel at elegosoft.com
> Subject: Re: [M3devel] HEADS UP: release engineering procedure clarification
>
> Quoting Jay K :
>
>>> the CM3 code work on some platform as well as changes to the
>>> scripts to correct building or regression testing.
>>
>> That's what I was doing.
>>
>> SOLgnu probably shouldn't require a custom gcc, and the changes,
>> e.g. in m3cc only affect SOLgnu/SOLsun.
>> You don't really have to rebuild everything due to that change.
>> That's just an artifact of how CVS triggers Hudson. You can keep
>> whatever preexisting built packages exist.
>>
>> Changes in scripts were so Cygwin sh could build NT386. Likewise.
>
> It's all OK until now AFAIK. We can selectively rebuild packages.
> I've just move the RC2 tag to reflect your changes in scripts
> and will rebuild the source archive.
>
> We haven't got any archives yet for SOLgnu, so we can change
> anything platform speccific there and move the tag forward, as long
> as it doesn't affect other targets.
>
> Olaf
>
>>
>> - Jay
>>
>>
>> ----------------------------------------
>>> Date: Sun, 2 Aug 2009 14:57:41 +0200
>>> From: wagner at elegosoft.com
>>> To: m3devel at elegosoft.com
>>> Subject: [M3devel] HEADS UP: release engineering procedure clarification
>>>
>>> Hi all,
>>>
>>> it seems I may need to explain the current procedure adopted for
>>> release engineering in order to avoid some confusion and chaos.
>>>
>>> (1) All release engineering occurs on the release_branch_cm3_5_8.
>>> The trunk is currently unaffected.
>>> (2) All RCs will be built from the release branch.
>>> (3) Fixes may be merged as necessary to the branch, but not
>>> arbitrary changes. Fixes comprise actual source fixes to make
>>> the CM3 code work on some platform as well as changes to the
>>> scripts to correct building or regression testing.
>>> (4) The tag release_CM3_5_8_RC2 defines the release candiate 2.
>>> I've made the last adaptions yesterday and started packaging
>>> the archives. make-dist.sh is currently supposed to just build
>>> this RC.
>>> (5) If we move the RC2 tag, we always need to rebuild a number of
>>> archives. We cannot do that indefinitely, as it takes a long
>>> time. If something is broken in RC2, it can be fixed in RC3.
>>> If we don't accept some bugs, we'll never make any release.
>>> (6) The Hudson regression and I think most of the tinderbox
>>> regression follows the release branch and not the trunk.
>>>
>>> Please heed these rules and help by building packages, improving
>>> the documentation and testing the available installation archives.
>>>
>>> I'm going to setup some automated tests for installation archives
>>> during the next days, but they will only cover some very basic
>>> aspects.
>>>
>>> Thanks for your cooperation,
>>>
>>> Olaf
>>> --
>>> Olaf Wagner -- elego Software Solutions GmbH
>>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
>>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
>>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
>>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
>>>
>
>
>
> --
> Olaf Wagner -- elego Software Solutions GmbH
> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
>