[ 
https://issues.apache.org/jira/browse/JAMES-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138603#comment-17138603
 ] 

Matthieu Baechler commented on JAMES-2586:
------------------------------------------

I do understand your arguments.

What I also understand is that you actually use JIRA in a way I'm not.

JIRA is designed for issue tracking, we describe problems, limitations, bugs 
but also improvements and ideas.

It's not a project management tool for me: I mean, I'm happy to search things 
in it as a knowledge base but I don't intend to empty the list of non-closed 
ticket as it's just unreachable on such a project: there will always be more 
things to do than contributors can handle.

It can be used as a project management tool when you start to assign tickets to 
a milestone and then you don't have to deal with how much open tickets there 
are in the system because you will filter on milestones.

You can also use something external to JIRA to handle project management (for 
example github project).

On the positive side of keeping things open: it allows to communicate intents. 
Other people can comment, contribute some related doc or code, etc. Would you 
search for closed issue for improvements or new features?



> Implement a Postgres-specific backend
> -------------------------------------
>
>                 Key: JAMES-2586
>                 URL: https://issues.apache.org/jira/browse/JAMES-2586
>             Project: James Server
>          Issue Type: New Feature
>            Reporter: Matthieu Baechler
>            Priority: Major
>
> James has a JPA implementation of most interfaces that allows to deploy it on 
> top of some popular RDBMS.
> However, while useful for some kind of applications, ORM are usually a bad 
> fit for applications requiring high performance like a mail server.
> As an abstraction, it also prevents from using advanced features of a given 
> RDBMS.
> For most usages, James would probably run great on top of Postgres, given 
> that we use advanced features to implement search, for example.
> A good strategy would be to implement all interfaces implemented by JPA with 
> a modern Postgres driver.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to