Closed Macadoshis closed 7 years ago
We moved the dbmaintain project to Github, when we started to work on it more. The Atlassian-Jira is no longer maintained. We never moved the tickets from there and just ignored them. If you still have problems with one of the issues listed there, please create a new ticket on Github.
And as the old saying goes : "A bug ignored is a bug fixed" Way to go fellas :beers: :clap: :100: :+1:
Hi @finsterwalder I see that you are one of original developers of DBMaintain. Can you explain why do you created a fork instead of maintaining original DBMaintain? I see that DBMaintain site was last updated in 2011 but in Maven Central there is some more recent artifacts. We would like to use DBMaintain in our quite big enterprise project but we can't trust to any forks and we'll prefer to use original technology instead or use any competitor like Liquebase or Flyway because we'll be sure that it will be supported in feature
Hi Sergey,
thanks for reaching out. Actually DBMaintain is now maintained by us on GitHub. The project was more or less abandoned and we picked it up. So this is the "original" version of DBMaintain, at least the one that is still maintained by us. This is in accordance with the old Maintainers. The old version was maintained by Tim Ducheyne. Only he has access to the official Website. It's a little hard to get a hold of him, so the site is no longer maintained. I know we should shut down the old site to avoid confusion, but we are not able to do that at this moment.
Greetings, Malte
On 7 September 2017 at 15:47, Sergey Ponomarev notifications@github.com wrote:
Hi @finsterwalder https://github.com/finsterwalder I see that you are one of original developers https://sourceforge.net/p/dbmaintain/_members/ of DBMaintain. Can you explain why do you created a fork instead of maintaining original DBMaintain? I see that DBMaintain site was last updated in 2011 but in Maven Central there is some more recent artifacts. We would like to use DBMaintain in our quite big enterprise project but we can't trust to any forks and we'll prefer to use original technology instead or use any competitor like Liquebase or Fluway because we'll be sure that it will be supported in feature
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/DbMaintain/dbmaintain/issues/23#issuecomment-327804427, or mute the thread https://github.com/notifications/unsubscribe-auth/AAMm7mwL5cEIJttRiCUux3ycwdAefRC3ks5sf_PjgaJpZM4Mm63a .
@stokito we are also using DbMaintain as standard tool in a big insurance company and are therefore interested in keeping the project alive.
Why are there still unresolved issues here https://unitils.atlassian.net/projects/DBM/issues/ and only 5 issues ever declared on github ? Are there 2 different life cycles ?