gobo-eiffel-develop — Development discussions

Re: [gobo-eiffel-develop] Bug tracker on sourceforge

[Colin P. A. <co...@co...>]

>>>>> "Eric" == Eric Bezault <er...@go...> writes:

    Eric> I did that. I was not sure whether we should just have a Bug
    Eric> Tracker, or also a Feature Request Tracker. What's your
    Eric> opinion?

I think yes.

And any feature requests not self-assigned by anyone after one month,
can be assigned to the requester :-)
-- 
Colin Adams
Preston Lancashire

Re: [gobo-eiffel-develop] Bug tracker on sourceforge

[Eric B. <er...@go...>]

Colin Paul Adams wrote:
>>>>>> "Bernd" == Bernd Schoeller <ber...@in...> writes:
> 
>     >> I received no suggestions yet for Categories and Groups to be
>     >> used in the bug tracker.
> 
>     Bernd> - For "Category", we go for the different subfolders under
>     Bernd> "library" and unter "src". Also, we might add "Other"
> 
> I would like XSLT, XPath and XPointer added as separate categories.

Oops, not done yet.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

Re: [gobo-eiffel-develop] Bug tracker on sourceforge

[Eric B. <er...@go...>]

Eric Bezault wrote:
> Bernd Schoeller wrote:
>> At Thu, 10 May 2007 13:43:25 +0200, Eric Bezault wrote:
>>> I received no suggestions yet for Categories and
>>> Groups to be used in the bug tracker.
>> Ok, let me try:
>>
>> - For "Group", we go for "Trunk" and version numbers of the releases
>>   as available unter 'tag'.
>>
>> - For "Category", we go for the different subfolders under "library"
>>   and unter "src". Also, we might add "Other"
>>
>> Tool.geant
>> Tool.gec
>> Tool.gelex
>> Tool.gelint
>> Tool.gepp
>> Tool.getest
>> Tool.gexace
>> Tool.gexslt
>> Tool.geyacc
>>
>> Lib.argument
>> Lib.kernel
>> Lib.lexical
>> Lib.math
>> Lib.parse
>> Lib.pattern
>> Lib.regexp
>> Lib.string
>> Lib.structure
>> Lib.test
>> Lib.time
>> Lib.tools
>> Lib.utility
>> Lib.xml
>>
>> Other
> 
> Considering that all tools start with "ge" and
> no library starts with "ge", perhaps we can get
> rid of the prefixes "Tool." and "Lib."?

I did that. I was not sure whether we should just have
a Bug Tracker, or also a Feature Request Tracker. What's
your opinion?

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

Re: [gobo-eiffel-develop] Bug tracker on sourceforge

[Colin P. A. <co...@co...>]

>>>>> "Bernd" == Bernd Schoeller <ber...@in...> writes:

    >> I received no suggestions yet for Categories and Groups to be
    >> used in the bug tracker.

    Bernd> - For "Category", we go for the different subfolders under
    Bernd> "library" and unter "src". Also, we might add "Other"

I would like XSLT, XPath and XPointer added as separate categories.
-- 
Colin Adams
Preston Lancashire

Re: [gobo-eiffel-develop] Next release

[Eric B. <er...@go...>]

Eric Bezault wrote:
> Jocelyn wrote:
>> If there are bug which impact Gobo, this is easier to have them fixed by
>> EiffelSoftware's team before the final 6.0 rather than trying to find
>> workaround.
> 
> We don't wait the release of Gobo to do that. What I'm
> concerned about is last minute bug discovery, which in
> my experience building the Gobo package happens quite
> often.

One solution could be that we release Gobo 3.6 just after
the last release candidate of EiffelStudio 6.0, and then
it's the responsibility of ISE to test that Gobo 3.6 still
works with the official EiffelStudio 6.0. How does that sound?

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

Re: [gobo-eiffel-develop] Bug tracker on sourceforge

[Bernd S. <ber...@in...>]

At Thu, 10 May 2007 17:07:55 +0100,
Colin Adams wrote:
> >Considering that all tools start with "ge" and
> >no library starts with "ge", perhaps we can get
> >rid of the prefixes "Tool." and "Lib."?
> 
> I agree - it's unecessarily ugly.

Sorry for my lack of esthetics, I am German ;-)

Bernd

Re: [gobo-eiffel-develop] Bug tracker on sourceforge

[Colin A. <col...@ho...>]

>From: Eric Bezault <er...@go...>

>Bernd Schoeller wrote:
> > At Thu, 10 May 2007 13:43:25 +0200, Eric Bezault wrote:
> >> I received no suggestions yet for Categories and
> >> Groups to be used in the bug tracker.
> >
> > Ok, let me try:
> >
> > - For "Group", we go for "Trunk" and version numbers of the releases
> >   as available unter 'tag'.
> >
> > - For "Category", we go for the different subfolders under "library"
> >   and unter "src". Also, we might add "Other"
> >
> > Tool.geant
> > Tool.gec
> > Tool.gelex
> > Tool.gelint
> > Tool.gepp
> > Tool.getest
> > Tool.gexace
> > Tool.gexslt
> > Tool.geyacc
> >
> > Lib.argument
> > Lib.kernel
> > Lib.lexical
> > Lib.math
> > Lib.parse
> > Lib.pattern
> > Lib.regexp
> > Lib.string
> > Lib.structure
> > Lib.test
> > Lib.time
> > Lib.tools
> > Lib.utility
> > Lib.xml
> >
> > Other
>
>Considering that all tools start with "ge" and
>no library starts with "ge", perhaps we can get
>rid of the prefixes "Tool." and "Lib."?

I agree - it's unecessarily ugly.

_________________________________________________________________
Reserve your place in history - Email Britain! 
http://www.emailbritain.co.uk/

Re: [gobo-eiffel-develop] Bug tracker on sourceforge

[Eric B. <er...@go...>]

Bernd Schoeller wrote:
> At Thu, 10 May 2007 13:43:25 +0200, Eric Bezault wrote:
>> I received no suggestions yet for Categories and
>> Groups to be used in the bug tracker.
> 
> Ok, let me try:
> 
> - For "Group", we go for "Trunk" and version numbers of the releases
>   as available unter 'tag'.
> 
> - For "Category", we go for the different subfolders under "library"
>   and unter "src". Also, we might add "Other"
> 
> Tool.geant
> Tool.gec
> Tool.gelex
> Tool.gelint
> Tool.gepp
> Tool.getest
> Tool.gexace
> Tool.gexslt
> Tool.geyacc
> 
> Lib.argument
> Lib.kernel
> Lib.lexical
> Lib.math
> Lib.parse
> Lib.pattern
> Lib.regexp
> Lib.string
> Lib.structure
> Lib.test
> Lib.time
> Lib.tools
> Lib.utility
> Lib.xml
> 
> Other

Considering that all tools start with "ge" and
no library starts with "ge", perhaps we can get
rid of the prefixes "Tool." and "Lib."?

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

Re: [gobo-eiffel-develop] Bug tracker on sourceforge

[Bernd S. <ber...@in...>]

At Thu, 10 May 2007 13:43:25 +0200, Eric Bezault wrote:
> As the Gobo project is growing, the mailing list is not
> enough anymore to track bugs, feature requests and
> development status. It has been asked that we use the
> facilities provided in SourceForge. I agree with that.
> But first we need to agree on a set of Categories and
> Groups in order to keep the bug tracker organized.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> I received no suggestions yet for Categories and
> Groups to be used in the bug tracker.

Ok, let me try:

- For "Group", we go for "Trunk" and version numbers of the releases
  as available unter 'tag'.

- For "Category", we go for the different subfolders under "library"
  and unter "src". Also, we might add "Other"

Tool.geant
Tool.gec
Tool.gelex
Tool.gelint
Tool.gepp
Tool.getest
Tool.gexace
Tool.gexslt
Tool.geyacc

Lib.argument
Lib.kernel
Lib.lexical
Lib.math
Lib.parse
Lib.pattern
Lib.regexp
Lib.string
Lib.structure
Lib.test
Lib.time
Lib.tools
Lib.utility
Lib.xml

Other

It is a little bit lengthy, but I think easy to understand.

Bernd

Re: [gobo-eiffel-develop] Bug tracker on sourceforge

[Eric B. <er...@go...>]

Colin Adams wrote:
> Can we start using this?
> 
> I want to enter the four long-standing bugs I have previously reported in 
> the XML parser.

Back in January I wrote:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*) Bug tracker:

As the Gobo project is growing, the mailing list is not
enough anymore to track bugs, feature requests and
development status. It has been asked that we use the
facilities provided in SourceForge. I agree with that.
But first we need to agree on a set of Categories and
Groups in order to keep the bug tracker organized.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I received no suggestions yet for Categories and
Groups to be used in the bug tracker.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

Re: [gobo-eiffel-develop] Next release

[Eric B. <er...@go...>]

Jocelyn wrote:
> Hi All,
> 
>> I don't care about "feature complete". It's unlikely that
>> new features will be used in this release of Gobo.
> Right, but at least no new features will be added which might raise new
> issues.
> 
>> I'm more concerned about "bug free" (and "ECF free" ;-)).
> 
> The advantage of testing against this "feature complete" release is to
> make sure no bug remains.

I would rather prefer spend time working, testing and
debugging the Gobo package than testing EiffelStudio.
But if ISE wants to test EiffelStudio with Gobo's code,
you are welcome.

>> Remaining bugs are really a challenge because we have to
>> find workarounds that work with all supported Eiffel compilers.
> 
> If there are bug which impact Gobo, this is easier to have them fixed by
> EiffelSoftware's team before the final 6.0 rather than trying to find
> workaround.

We don't wait the release of Gobo to do that. What I'm
concerned about is last minute bug discovery, which in
my experience building the Gobo package happens quite
often.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

Re: [gobo-eiffel-develop] Next release

[Jocelyn <li...@dj...>]

Hi All,

> I don't care about "feature complete". It's unlikely that
> new features will be used in this release of Gobo.
Right, but at least no new features will be added which might raise new
issues.

> I'm more concerned about "bug free" (and "ECF free" ;-)).

The advantage of testing against this "feature complete" release is to
make sure no bug remains.
> Remaining bugs are really a challenge because we have to
> find workarounds that work with all supported Eiffel compilers.

If there are bug which impact Gobo, this is easier to have them fixed by
EiffelSoftware's team before the final 6.0 rather than trying to find
workaround.

Now, this is up to Eric and GoboEiffel team to decide.

-- Jocelyn

[gobo-eiffel-develop] Bug tracker on sourceforge

[Colin A. <col...@ho...>]

Can we start using this?

I want to enter the four long-standing bugs I have previously reported in 
the XML parser.

_________________________________________________________________
Play your part in making history - Email Britain! 
http://www.emailbritain.co.uk/

Re: [gobo-eiffel-develop] Next release

[Eric B. <er...@go...>]

Jocelyn wrote:
> Hi
> The last release of Eiffel6.0 is "feature complete".
>     http://www.eiffelroom.com/blog/manus_eiffel/eiffelstudio_6_0_coming_soon
>     http://eiffelsoftware.origo.ethz.ch/downloads/builds/
> 
> So I guess this can be used to test gobo, and this way next release of
> Gobo could be included into ISE's delivery.

I don't care about "feature complete". It's unlikely that
new features will be used in this release of Gobo.
I'm more concerned about "bug free" (and "ECF free" ;-)).
Remaining bugs are really a challenge because we have to
find workarounds that work with all supported Eiffel compilers.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

Re: [gobo-eiffel-develop] Next release

[Bernd S. <ber...@in...>]

AFAIK, current Gobo SVN does not include major new functionality, but
significant bug-fixes. So, 3.6 will not contain may experimental
features that need extensive testing, but contains some improvements
that I would love to see included in 6.0. 

Releasing 3.6 shortly after 6.0 would not do any good: this would make
it necessary to cope with many developers still using 3.5 and we would
need to support two releases.

Bernd

At Thu, 10 May 2007 09:45:53 +0200,
Eric Bezault wrote:
> 
> Colin Adams wrote:
> > It's now about six weeks short of six months since 3.5 was released. And 
> > Eiffel Studio 6.0 will be released in about a month's time. So I think it's 
> > time to consider a new release soon.
> 
> Should it happen before or after the release of ISE 6.0?
> Before means that it can be included into ISE's delivery.
> After means that we can test it with the official version of ISE 6.0.
> 
> -- 
> Eric Bezault
> mailto:er...@go...
> http://www.gobosoft.com
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> gobo-eiffel-develop mailing list
> gob...@li...
> https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop

Re: [gobo-eiffel-develop] Next release

[Jocelyn <li...@dj...>]

Hi
The last release of Eiffel6.0 is "feature complete".
    http://www.eiffelroom.com/blog/manus_eiffel/eiffelstudio_6_0_coming_soon
    http://eiffelsoftware.origo.ethz.ch/downloads/builds/

So I guess this can be used to test gobo, and this way next release of
Gobo could be included into ISE's delivery.

-- Jocelyn

On 5/10/2007 09:45 AM, Eric Bezault wrote:
> Colin Adams wrote:
>   
>> It's now about six weeks short of six months since 3.5 was released. And 
>> Eiffel Studio 6.0 will be released in about a month's time. So I think it's 
>> time to consider a new release soon.
>>     
>
> Should it happen before or after the release of ISE 6.0?
> Before means that it can be included into ISE's delivery.
> After means that we can test it with the official version of ISE 6.0.
>
>   

Re: [gobo-eiffel-develop] Next release

[Colin A. <col...@ho...>]

I would suggest just before.
That is, if Manu can provide a good estimate of when the last weekly 
pre-release of 6.0 is due, then we test Gobo thorougly the week before that 
on SE 1.2r7, GEC and ISE 5.6 and 5.7.

Then when the (expected) last pre-release comes out, we have several days 
for checking against that. If it looks good, then release Gobo 3.6/4.0.

If ISE then manage to break it before releasing 6.0, that's just tough.

>From: Eric Bezault <er...@go...>

>Colin Adams wrote:
>>It's now about six weeks short of six months since 3.5 was released. And 
>>Eiffel Studio 6.0 will be released in about a month's time. So I think 
>>it's time to consider a new release soon.
>
>Should it happen before or after the release of ISE 6.0?
>Before means that it can be included into ISE's delivery.
>After means that we can test it with the official version of ISE 6.0.
>
>--
>Eric Bezault
>mailto:er...@go...
>http://www.gobosoft.com

_________________________________________________________________
Play your part in making history - Email Britain! 
http://www.emailbritain.co.uk/

Re: [gobo-eiffel-develop] Next release

[Eric B. <er...@go...>]

Colin Adams wrote:
> It's now about six weeks short of six months since 3.5 was released. And 
> Eiffel Studio 6.0 will be released in about a month's time. So I think it's 
> time to consider a new release soon.

Should it happen before or after the release of ISE 6.0?
Before means that it can be included into ISE's delivery.
After means that we can test it with the official version of ISE 6.0.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

[gobo-eiffel-develop] Next release

[Colin A. <col...@ho...>]

It's now about six weeks short of six months since 3.5 was released. And 
Eiffel Studio 6.0 will be released in about a month's time. So I think it's 
time to consider a new release soon.

_________________________________________________________________
Could you be the guest MSN Movies presenter? Click Here to Audition 
http://www.lightscameraaudition.co.uk

Re: [gobo-eiffel-develop] XM_XSLT_NODE_FUNCTION_CALL_FLATTENER

[Colin P. A. <co...@co...>]

>>>>> "Eric" == Eric Bezault <er...@go...> writes:

    Eric> Should XM_XSLT_NODE_FUNCTION_CALL_FLATTENER be removed?

Yes, I missed that one.

I'll do it now.
-- 
Colin Adams
Preston Lancashire

[gobo-eiffel-develop] XM_XSLT_NODE_FUNCTION_CALL_FLATTENER

[Eric B. <er...@go...>]

Should XM_XSLT_NODE_FUNCTION_CALL_FLATTENER be removed?

[VTCT] class XM_XSLT_NODE_FUNCTION_CALL_FLATTENER (39,29): type based on 
unknown class XM_XSLT_FUNCTION_CALL_PACKAGE.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

Re: [gobo-eiffel-develop] SVN properties for new files

[Eric B. <er...@go...>]

Colin Paul Adams wrote:
>>>>>> "Eric" == Eric Bezault <er...@go...> writes:
> 
>     Eric> I know that you don't know why this is happening, but I
>     Eric> would rather prefer that you check and fix these properties
>     Eric> in your new added files yourself, rather than doing it
>     Eric> myself.
> 
> I've made a note of this, for next time.

Thanks.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

Re: [gobo-eiffel-develop] SVN properties for new files

[Colin P. A. <co...@co...>]

>>>>> "Eric" == Eric Bezault <er...@go...> writes:

    Eric> I know that you don't know why this is happening, but I
    Eric> would rather prefer that you check and fix these properties
    Eric> in your new added files yourself, rather than doing it
    Eric> myself.

I've made a note of this, for next time.
-- 
Colin Adams
Preston Lancashire

Re: [gobo-eiffel-develop] SVN properties for new files

[Eric B. <er...@go...>]

Hi Colin,

You added new files to SVN yesterday and today, and they still suffer
from the same problem. I had to add the svn:keywords property to all
of them, and the svn:eol-style property to reverse3.xsl (otherwise we
got \n instead of \r\n under Windows when viewing the file in Notepad).

I know that you don't know why this is happening, but I would rather
prefer that you check and fix these properties in your new added
files yourself, rather than doing it myself.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com


Eric Bezault wrote:
> col...@us... wrote:
>> Added Paths:
>> -----------
>>     
>> gobo/trunk/library/xml/xpath/expression/xm_xpath_arithmetic_signature.e
>>     gobo/trunk/library/xml/xpath/sort/xm_xpath_exception_routines.e
>>     gobo/trunk/library/xml/xslt/sort/xm_xslt_sorted_node_iterator.e
> 
> When adding new files to SVN, please make sure that the following
> properties are set correctly,
> 
>    svn:eol-style   native
>    svn:keywords    Author Date Id Revision
> 
> as indicated in this message:
> 
>    http://www.nabble.com/Subversion-tf3117603.html
> 
> Here the property svn:keywords is missing. I just added it.
> 

Re: [gobo-eiffel-develop] Postcondition failure in {DS_HASH_TABLE}.search_position

[Colin P. A. <co...@co...>]

>>>>> "Colin" == Colin Paul Adams <co...@co...> writes:

>>>>> "Eric" == Eric Bezault <er...@go...> writes:
    Eric> There are two reasons why you could get a postcondition
    Eric> violation in this routine. Either this routine (or its
    Eric> postcondition) has a bug, or your hash table contains
    Eric> mutable keys whose comparison criterion or hash code has
    Eric> changed since it was first inserted.

    Colin> I've thought of another possibility.  The items are
    Colin> datetimes in different time zones.  It may be that I have
    Colin> two items that compare equal, but their hash codes are not
    Colin> equal.

Yes that was the problem. 
I had actually thought about it, it seems, but just got it wrong.

Fixed now.
-- 
Colin Adams
Preston Lancashire