|
Keeping track of cvs
|
|
By hurstdog , Section Project []
Posted on Thu Apr 05, 2001 at 12:00:00 PM PST
|
 |
|
As of right now there is no one place that all of the latest cvs commits
and adds are posted to (unless you count the web interface to the cvs repository, but then you need to look on a file-by-file basis). I've looked into setting up a scoop-cvs list, that
would get emailed with every cvs commit, but sourceforge doesn't seem to have
that feature presently. I did file a feature request though. What follows
below is a few things I've been thinking about for alternatives
to having a scoop-cvs list.
|
The main problem is letting scoop admins know when we add a new feature, or
fix a particular bug, or speed up scoop somehow, in the cvs tree. So how
could Rusty and I let you all know whats happening, preferably with little
extra effort on our parts? ;-) Here are a few solutions I've thought about,
and would like your input on.
- The first possibility is a section or topic on scoop, that only me and
rusty post to, that would just be notes about the cvs code. Every major feature
or bug we add or fix we would post a small note to this section, so people
who are interested would be able to periodically check this section, and
see what they are missing. On a side note: this could either be done by
having the stories auto-posted, or by having them go through the queue, so
relevant big fixes would go on the main page if necessary.
- The second possibility would be a list, either on hurstdog.org or
kuro5hin.org (probably kuro5hin.org, less chance of the line going down ;-)
that rusty and I mail to with every commit. With the same type of info
as would get posted to scoop.
- Yet another possibility, is for instead of being posted to scoop.k5,
it would get posted to a different page, and just pushed into the front on
the top, with a date/time stamp, and a small section with notes on the commit.
Of course, none of these possibilities are feasable if they are not easy
to use, on both ends. I don't want to spend an extra couple minutes every
commit to post a story, or to write an email, and rusty doesn't either. We
actually had this problem with updating the VERSION file in the latest releases
of scoop (in both trees), so rusty threw together a nice little cvs wrapper
that would update it every time for us. One possibility is to expand the
capabilities of the wrapper, and have it auto-post a story with the contents
of the commit message to scoop.k5, or to an email list, or to a small 'stats'
page like in option #3. But that would be on our end. Not the users' end.
Anyway, the main thing I'm looking for here is suggestions. Can you think
of a better way to do it? What way would you prefer? Posting stories is nice,
because we get commenting and searching along with it, but it adds lots of
noise to scoop.k5 (yes, many commits could be considered noise ;-) . The email
idea would fix that noise problem, but then you get a more full inbox (not that
much more full, but still). I'm kind of leaning towards the 3rd approach,
that would just put all of the commits on one static html page. But what do
you think? |
|
|
Story Views
|
|
24 Scoop users have viewed this story.
|
|
