Feature Updates

[Owen Winkler]

One of the challenges when producing a release is coming up with a list
of concrete things that have been updated or added since the last version.

I've created a wiki page for version 0.7 where we can add new high-level
line items that would be useful in a release announcement.

Obviously, there's nothing there yet, but hopefully it'll fill out
nicely. It could also be a useful gauge of when the time becomes
appropriate for a new release. Not all of the items might be listed in
the release announcement, but at least it'll exist to pull things from,
rather than trying to figure out what each commit was trying to do from
the svn logs.

http://wiki.habariproject.org/en/Releases/0.7/Changes

Owen

[Christian Mohn (h0bbel)]

Is there a way to parse something like "New Feature: xxx" from the commit
log and somehow autogenerate such a list?

Christian

[Arthus Erea]

Indeed, I think that would make this much more manageable.

Maybe some of our Trac/svn gurus could put something together?

Alternately, we could probably develop such a system on top of
InDefero (if that is switched to).

If we don't auto-generate the list, could we provide relevant revision
numbers on the wiki page?

[Christian Mohn (h0bbel)]

In any case, if we can maintain some kind of structure to the commit
messages we should be able to just grep for it at least. :)

[Chris Meller]

Just as it's not really practical to look down the list of commit messages and quickly glean what was being done, I don't think it's really feasible to expect everyone to "tag" their commits for the same reasons: often it's a smaller part of a larger feature... should you have to tag them all, tag what you think is the final, what?

I suspect that anything like that would only ever be minimally useful due to the patchy nature of usage.

[Christian Mohn (h0bbel)]

Well, that depends on discipline, doesn’t it? If you start on a _new_ feature, that should be tagged as such. Seems easy enough for me?

 

From: habar...@googlegroups.com [mailto:habar...@googlegroups.com] On Behalf Of Chris Meller
Sent: 7. april 2009 19:23
To: habar...@googlegroups.com
Subject: [habari-dev] Re: Feature Updates

 

Just as it's not really practical to look down the list of commit messages and quickly glean what was being done, I don't think it's really feasible to expect everyone to "tag" their commits for the same reasons: often it's a smaller part of a larger feature... should you have to tag them all, tag what you think is the final, what?

[Owen Winkler]

Chris Meller wrote:
> Just as it's not really practical to look down the list of commit
> messages and quickly glean what was being done, I don't think it's
> really feasible to expect everyone to "tag" their commits for the same
> reasons: often it's a smaller part of a larger feature... should you
> have to tag them all, tag what you think is the final, what?
>
> I suspect that anything like that would only ever be minimally useful
> due to the patchy nature of usage.

Yeah, that's one reason why I created the wiki page. If you forget to
add the feature in the commit log, even someone else could notice and
add it to the wiki.

It might be useful to add an automated feature to the post-commit hook
to look for things, but in the end that's just a tool to help the
primary goal of listing high-level new features somewhere.

Owen

[Michael Harris]

2009/4/8 Owen Winkler <epi...@gmail.com>:

Worthwhile features are also likely to be added over multiple commits
too. What commit added ACL ? :)

--
Michael C. Harris, School of CS&IT, RMIT University
http://twofishcreative.com/michael/blog
IRC: michaeltwofish #habari

[rick c]

Whatever the level of automation to generate the data, from fully
manual to fully manual, such a page is better than looking over
several months worth of commits to pick out features to add to a
release announcement. Some things may be missed, some may get added in
too much detail. Either way a human has a starting place to distill
the data into information for a new release announcement.

Rick

On Apr 7, 10:14 pm, Michael Harris <michael.twof...@gmail.com> wrote:
> 2009/4/8 Owen Winkler <epit...@gmail.com>: