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: [email protected] [mailto:[email protected]] On 
Behalf Of Chris Meller
Sent: 7. april 2009 19:23
To: [email protected]
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?

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

On Tue, Apr 7, 2009 at 12:25 PM, Christian Mohn (h0bbel) <[email protected]> 
wrote:


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

Christian


-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Owen Winkler
Sent: 7. april 2009 17:28
To: [email protected]
Subject: [habari-dev] Feature Updates


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










--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to