geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Hogstrom <m...@hogstrom.org>
Subject Re: What do we do about fixable problems in M5?
Date Wed, 05 Oct 2005 15:59:04 GMT
>	 <87708F80-3E95-4CDE-8960-DF5204709EC9@apache.org> <b8b1243f0510050852v26f83da4x3b59160814d6346f@mail.gmail.com>
In-Reply-To: <b8b1243f0510050852v26f83da4x3b59160814d6346f@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MMS-Smtp-Program: Macallan-Mail-Solution; Version 4.6.0.1
X-MMS-Smtp-Auth: Authenticated As matt@hogstrom.org
X-MMS-Smtp-Mailer-Program: Macallan-Mail-Solution; Version 4.6.0.1

I probably screwed up and viewed any problem that required the customer to do 
something as fixable issue.  If this is the case my bad.

Matt

Kevan Miller wrote:
> As Joe has pointed out, I've pulled the installer issue into this discussion
> and improperly associated it with the config.tomcat.xml issue.
> 
> The reticence I remarked upon was from the original posts on this thread. I
> wasn't attempting to be critical. Any reticence would be only natural and in
> fact proper -- we can't ship a new Milestone for every problem we find.
> 
> In answer to your question -- AFAIK, the stop-the-presses issue lies solely
> with the Installer. I'm not familiar with the implementation/configuration
> of the installer, but I assume that changing the default port number for
> Tomcat would fix the problem. Perhaps this is already in process? I'm not
> able to download the installer, now...
> 
> There are known issues with M5 (now including Stefan's issue). However,
> they're issues properly handled via errata, build-from-HEAD, nightly build,
> etc.
> 
> --kevan
> 
> On 10/5/05, Geir Magnusson Jr. <geirm@apache.org> wrote:
> 
>>
>>On Oct 5, 2005, at 10:18 AM, Kevan Miller wrote:
>>
>>
>>>Without a really big disclaimer on the download page, my guess is
>>>that approximately 100% of new-to-Geronimo M5 Installer users will
>>>run into this problem. All you have to do is keep hitting "Next". I
>>>did. I just never started my "installed" server, because I'd
>>>already tested the zipped/tarred version of code (my mistake).
>>>
>>>I don't think an errata is sufficient and I don't see how we can
>>>ignore such a visible issue. This may be a bit heretical, but one
>>>option is not to release the installer. Although this is a server
>>>issue, you don't hit this problem in normal usage when running from
>>>an zip/tar "install" (at least I haven't run into any other
>>>problems, am I missing something?).
>>>
>>>Most first-time users will choose the install download thinking
>>>they're making their lives easier, when actually, they've just made
>>>their lives more difficult. Although some last-minute hard work
>>>went into the installer, IMO, the M5 installer is of limited value
>>>for first-time Geronimo users. I also think that the current
>>>installer is actually a configuration utility in disguise -- we
>>>should start separating concerns...
>>>
>>>BTW, I assume that actually fixing the underlying problem means
>>>rerunning the TCK tests? Thus the reticence for fixing?
>>
>>I'm not sure where you are seeing reticence.
>>
>>If just fixing the installer fixes it, then that's easy. If the
>>problem is only in the installer, we'll just remove that link for now
>>from the download page immediately. Please confirm that it's only
>>the installer.
>>
>>geir
>>
>>
>>
>>>--kevan
>>>
>>>On 10/5/05, Geir Magnusson Jr. <geirm@apache.org> wrote:
>>>On Oct 5, 2005, at 8:30 AM, Matt Hogstrom wrote:
>>>
>>>
>>>>I think that will work but users won't find Geronimo incredibly
>>>>useful if they have to pull a whole new build to fix a single
>>>
>>>problem.
>>>
>>>Which will work?
>>>
>>>i think the errata is necessary so people will know what to do. As
>>>for a quick M6? I think it depends on the %-age of people that will
>>>hit the problem.
>>>
>>>
>>>>I discovered a similar problem in TranQL that the 1.1 SNAPSHOT
>>>>doesn't generate the right SQL syntax for DB2 and had to tweak the
>>>>Syntax Generator. So the option going forward is for someone to
>>>>pull TranQL 1.2-SNAPSHOT which wil most likely break their build
>>>>too because of the serialization problem (probably not likely with
>>>>my example but a high probability for other types of fixes).
>>>
>>>Does this mean as of now, we have a problem w/ DB2?
>>>
>>>
>>>>Sachin had the right idea of highlighting the issues with
>>>>serialVersionUIDs but that was part of a larger problem. I'll open
>>>>a feature JIRA that focuses on improved serviceability which would
>>>>encompass these recurring issues and we'll look for someone to step
>>>>up to the plate and put a strategy together.
>>>>
>>>
>>>yes, I think that's a different (but very important) issue altogether.
>>>
>>>
>>>
>>>>Thoughts?
>>>>
>>>
>>>Go man, go...
>>>
>>>
>>>>- Matt
>>>>
>>>>Geir Magnusson Jr. wrote:
>>>>
>>>>
>>>>>On Oct 4, 2005, at 11:24 PM, David Jencks wrote:
>>>>>
>>>>>
>>>>>>Stefan Schmidt has found our first configuration problem in M5,
>>>>>>namely that the listener name in the ejb builder in
>>>>>>config.tomcat.xml points half to tomcat and half to jetty. This
>>>>>>is easy to fix by hand (change JettyWebContainer to
>>>>>>TomcatWebContainer). However I doubt we want to rerelease M5 to
>>>>>>fix this. What do we want to do about issues like this? One
>>>>>>possibility is to have an "errata" page clearly linked from the
>>>>>>download page.
>>>>>>
>>>>>
>>>>>That's a great idea.
>>>>>
>>>>>
>>>>>>There must be some other possibilities, any ideas?
>>>>>>
>>>>>
>>>>>1) Can we capture this as some kind of functional test to prevent
>>>>>from happening again?
>>>>>2) how long would it take to fix on branch/m5 (and head) and do a
>>>>>M6 tag off of branch/m5 (if people don't find that too
>>>>>nauseating) and release that?
>>>>>geir
>>>>>
>>>>
>>>>
>>>--
>>>Geir Magnusson Jr +1-203-665-6437
>>>geirm@apache.org
>>>
>>>
>>>
>>
>>--
>>Geir Magnusson Jr +1-203-665-6437
>>geirm@apache.org
>>
>>
>>
> 
> 


Mime
View raw message