Re: App for storing ChangeLogs in database

Am 07.02.2015 um 00:31 schrieb Russell Keith-Magee: ... To me - it sounds like something pretty closely tied to your own development process, branching policies, and customer relationships. I have no difficulty seeing how this could be implemented as a Django app - and a fairly trivial one

Re: App for storing ChangeLogs in database

On Fri, Feb 6, 2015 at 8:24 PM, Thomas Güttler wrote: > Hi, > > we want to make the changes in our applications better visible for our > customers. > > We use several git repos: > > - foo_customer: Here settings.py lives. It is quite small. > > - foo_core: Central part of

Re: App for storing ChangeLogs in database

I don't have a solution for you but maybe you are just looking for strategies? Like you, I don't like showing users the commit messages. We use Trac for our ticketing and insist no work gets done without a ticket. We added a custom field to Trac called "Release note". So when someone raises a

App for storing ChangeLogs in database

Hi, we want to make the changes in our applications better visible for our customers. We use several git repos: - foo_customer: Here settings.py lives. It is quite small. - foo_core: Central part of our application. The same code gets used for several customers. - foo_plugin_bar: Just