[M3devel] RC2 Release Engineering Status and Trac-king
Jay K
jay.krell at cornell.edu
Sat Jul 18 14:58:29 CEST 2009
> cm3ide crash
still happens -- if /cm3/examples doesn't exist.
Doesn't crash if empty /cm3/examples created.
To get it to crash, click on the "examples" link.
Now I can't debug it, gdb won't debug my AMD64 binary, wierd.
> m3tohtml crash
I was able to see it crash, and then not crash with my config file changes.
Since it is run in the Tinderbox though, that should provide extra confirmation.
remove/simplify dynamic library version numbering?
> Can be left alone.
I meant specifically for this release.
For next release I'd like to reconsider.
- Jay
From: jay.krell at cornell.edu
To: wagner at elegosoft.com; m3devel at elegosoft.com
Date: Sat, 18 Jul 2009 12:27:46 +0000
CC: admins at elego.de
Subject: Re: [M3devel] RC2 Release Engineering Status and Trac-king
My opinion on some of these:
cm3ide crash (NIL pointer?) #1002
probably fixed but needs retesting
m3tohtml crash
probably fixed but needs retesting
broken m3overrides
probably fixed but need to wait for Tinderbox to confirm
I can migrate more of them to the one master, but that's not required.
And there are some variations that need to be preserved, so it has to be all
human reviewed.
remove/simplify dynamic library version numbering?
Can be left alone.
I advocate removing the versions entirely.
However the "complexity" here is very hidden anyway.
m3gdb doesn't build on Darwin
I think we punt on this for this release.
Just update the distribution building to skip it.
I think the fix is probably to import Apple's fork.
I don't like it either, but it's probably the "best" way (short of
the unlikely Apple/FSF merge).
mentor startup crash on Darwin
PPC_DARWIN? All Darwin?
ie: What I reported?
Yes sounds bad.
Maybe the same thing as formsedit.
- Jay
> Date: Sat, 18 Jul 2009 14:18:22 +0200
> From: wagner at elegosoft.com
> To: m3devel at elegosoft.com
> CC: admins at elego.de
> Subject: [M3devel] RC2 Release Engineering Status and Trac-king
>
> We really need to use some tools to help us keep (or gain?)
> control of the release process. Trac has been available for more
> than a year, but nobody has actively used it. Maybe this is a good
> time now :-)
>
> I've started by sketching a roadmap with RC2, 5.8 and 5.9.
> See here: https://projects.elego.de/cm3/roadmap
>
> Please add all the problems that were just reported via mail
> to the trac database with `new ticket':
> https://projects.elego.de/cm3/newticket.
>
> I've tried it for the cm3ide crash (ticket 1002); it seems to work
> fine. Some older bug reports are also still unresolved, but we can
> check them later.
>
> It would also be helpful if all active developers had personalized
> access and would help updating the tickets and the WiKi. Please send
> mail to admins(at)elego.de to obtain an account from Michael or Joffrey.
>
> Please let's use this; I'm afraid we'll lose control without it.
>
> It also has the advantage that the HTTP GUI is accessible from the
> customer network I'm usually working on (while everything else is
> blocked).
>
> Thanks in advance 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090718/ff81fbcf/attachment-0002.html>
More information about the M3devel
mailing list