On Sat, May 31, 2008 at 12:40 PM, Ingmar Vanhassel <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I think it'd be a good idea to generate ChangeLogs from the git commit
> messages. I usually write the same information in both ChangeLog and
> commit message, so we're needlessly duplicating information.
Works for me as long as people are not doing entire novels as their
messages (I like keeping commit messages fairly short so I can easily
get an overview of the last $X commits). I can't remember ever doing
so myself however so I don't expect that to be a problem.
>
> Since ChangeLogs are meant for users, I'd like to generate them on the git
> server, as part of the metadata generation, and distribute them in our
> rsync:// checkouts (and remove them from our git repositories).
> This assumes that at some point we'll provide rsync:// checkouts
> for all our hosted supplemental repositories.
Sounds good.
>
> Anything else we want to change wrt this?
> - Move them to metadata/changelogs/{exlibs,packages,profiles}
> - Keep or remove email adresses?
> - Keep our email adresses somewhere in the tree, say metadata/authors?
I'd say keep email addresses in the ChangeLogs. As to where the
ChangeLogs should be stored I'd just stick 'em in the package
directories for now and then look at it again when we figure out what
to do about categories/tags and probably end up restructoring
everything.
>
> Thinking out loud, we could have tags in the git commit messages to
> automate some things a bit more, the way KDE does in their SVN repo.
> - fixes: Reference bug, mark as RESOLVED FIX.
> - see: Reference bug.
> - thanks: Recognize contributors
This would probably be nice. I'm not sure which tags we'd need but
that shouldn't be too hard to work out imo.
Regards,
Bryan Østergaard
_______________________________________________
Exherbo-dev mailing list
[email protected]
http://lists.exherbo.org/mailman/listinfo/exherbo-dev
