Re: [Babeldoc-devel] PipelineStageFactory

[Bruce M. <br...@mc...>]

Erik, all,

I am quite open to delaying the release of 1.0 until we have gotten this 
sorted out.  I would prefer that we follow your efforts so that we may 
immediately reap the benefits of your work.  Basically I agree with Dejan 
here - we need not rush to 1.0 after moving patiently for this long year.

regards,
Bruce.

On Tuesday 22 April 2003 03:45 pm, ek...@ba... wrote:
> Gentlemen, the last thing I want to do is be the cause of the delay of the
> initial release.  I "walked onto" this project very late in your
> development cycle and have been quite a drain on your resources in order
> to get the assistance I need in implementing this for my purposes.  I
> never expected the software to be "custom built" for my needs.  The
> product will never be "all things to all people".
>
> The issue of Exceptions may be a touchy one ... I certainly don't want to
> go around changing the method signatures of the majority of methods in the
> system if the current functionality meets most people's needs right now.
> Whether I discovered a rare instance of an exception not being handled
> well or if this "issue" is propogated all throughout the system, I have no
> idea.  I get the impression that what I've proposed today may be a bigger
> modification than is desired at this point.
>
> As you are aware, I have incredibly tight deadlines for production
> implementation (less than 4 weeks at this point) and hence may not be able
> to provide the type of "community support" that most other participants in
> an open-source project can provide.  And I don't want other people
> spending their time and effort making modifications solely for my
> consumption.
>
> I am equally open to the following options:
> 1. Me implementing my own Logging extension that throws a RuntimeException
> whenever an Error Log request is made, thereby affecting no one else
> 2. Us investigating which discarded exceptions are legitimate and which
> need to be addressed and dividing the work to do it ... this can take a
> tremendous amount of analysis for someone not familiar with the codebase
> 3. Me diverging from the codebase at this point, implementing my own
> exception handling, and perhaps merging back after 1.0 is released.
>
> I'm open to any of the above.  Bruce, I look to you for guidance on this.
> Thanks.
>
> Erik
>
>
>
> Sent by:        bab...@li...
> To:     bab...@li...
> cc:
> Subject:        Re: [Babeldoc-devel] PipelineStageFactory
>
>
> If you asking me I would not hurry with this realase.
>
> We do plan some changes in core module that could
> impact on all other modules. I guess there will be
> more changes like this since requirements that Erik
> has are pretty different than those that you had when
> you have started to write Babeldoc and those that I
> had in my projects. This will require a lot of
> testing.  Some aspects that was not important for us
> will be important for Erik's project so he will
> probably do more changes (which is good thing because
> it will improve Babeldoc and make it applicable to
> problems that was not initialy planned).
>
>
>
> Also, note that I will be on vacation between April
> 25th and May 5th.
>
> Dejan
>
> --- Bruce McDonald <br...@mc...> wrote:
> > Dejan,
> >
> > The release, all things being equal will go out on
> > May 2 2003
> >
> > regards,
> > Bruce.
>
> __________________________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo
> http://search.yahoo.com
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
>
>
>
> ________________________________________________________________________
> The information in this e-mail, and any attachment therein, is confidential
> and for use by the addressee only. If you are not the intended recipient,
> please return the e-mail to the sender and delete it from your computer.
> Although The Bank of New York attempts to sweep e-mail and attachments for
> viruses, it does not guarantee that either are virus-free and accepts no
> liability for any damage sustained as a result of viruses.