Re: [Babeldoc-devel] Preparing 1.0 release

[Dejan K. <dej...@nb...>]

You are right about JMS.

Talking about documentation, do you speak Serbian?  ;-)
I am planning to give them only offical Babeldoc documentation. I am also
writing some materials for one conference here, but that will be in Serbian,
too!
Dejan



----- Original Message ----- 
From: ek...@ba...
To: Dejan Krsmanovic
Cc: Bruce McDonald ; bab...@li...
Sent: Friday, May 09, 2003 2:31 PM
Subject: Re: [Babeldoc-devel] Preparing 1.0 release



<<
One tehnical question. If we have branch v1_0 for bug fixes and v1_1 for new
development, what should go in HEAD branch?  I think new development should
go in HEAD branch (main branch) and after every major release we should
create branch for bugfixes. For other releases we could just use tags (as we
did by now).
>>

Agreed.

<<
Documents in queues should
be serialized so in case of some accident they will be loaded application
starts next time. I am still not sure if we should use JMS for queueing or
write class for this stuff.
>>

Remember that JMS pretty much mandates that Babeldoc be inside of a J2EE
container in order to use scanners in your scenario ... I'm not sure that
was the original intent of the project.

<<
By the way, next week I am starting Babeldoc training for 4 employees in my
company.
>>

You might want to share any documentation / handouts you provide for them
with this group.
________________________________________________________________________
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.