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 an example. There are several optional plugins. Here is my current road map: A nice interface for the customer implies: The changes need to be stored in the database. This makes it easy to sort and filter the changes. The origins of the changes are the git repos. I don't want to show the customer our commit messages. I want a manual step from commits to ChangeLog. But that's ok. This could be optimized later. Use Case: A developer merged a feature branch into foo_core. He needs to create a ChangeLog. The ChangeLog gets stored into the git repo, but on the next deploy some tool reads the new changes and puts them into the database. ChangeLogs need to be tag-able: You can apply tags like "performance-improvement" "new-feature" "bug-fix". I searched the web, but could not find something like this. Before I start to code, I want to get some feedback: What do you think? How do you handle your ChangeLogs. PS: Our customers are normal (non programmers) people. They don't want to see diffs or commit messages they don't understand. -- Thomas Güttler http://thomas-guettler.de/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/54D4B260.8030402%40tbz-pariv.de. For more options, visit https://groups.google.com/d/optout.
