Bernd Fondermann ha scritto:
On Tue, Jun 24, 2008 at 6:41 PM, Bernd Fondermann
<[EMAIL PROTECTED]> wrote:
On Tue, Jun 24, 2008 at 5:40 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
I would like to know if, after almost 2 years we use it, people still think
that STATUS file in trunk is useful.
http://svn.apache.org/repos/asf/james/server/trunk/STATUS

I think it contains outdated content. Something gone wrong with its use. How
can we improve this situation?
remove outdated content. I'll have a quick look.

I think the most useful information is the sandboxes list,
+1

but it seems just
the wrong place.
to me it seems ok.

I thought it was wrong (for sandboxes) just because people working on a sandbox can easily update files inside the sandbox, not a file in trunk.
Often you don't even have a trunk checkout when you work on a sandbox.

My opinion is that we should try to mantain a STATUS file for each sandbox
trying to use dates in stuff we write so that people looking into sandboxes
would have an idea of the motivation, the status and when the last update to
the status happened.
I'd rather keep a central file at a central place. But I agree that
sandbox info should be uptodate, more or less ;-).

 Bernd

I did a quick check and cannot find anything wrong with the file
except it is outdated.

There is nothing that could be worse than being outdated: it is a status file. Its only purpose is representing the *current* status :-)

I still believe it could be useful if it was more uptodate.

Ok, let's say that on 27/06/2009 I'll propose to remove it in the case it will contain the same content as of today.

Most of the votes and proposals tracked there are not even resolved
on-list. So this only reflects our own habits which is sometimes good
to remember as a motivation to try and improve. ;-)

The only open vote, is IMO closed, but you probably remember the whole story. I will not take the responsibility of updating it.

Next-minor/Next-major/Next-greater have no more meanings to most of us.

Maybe we should remind ourselves from time-to-time (maybe taking a
looming board report as a trigger) to maintain it.

Let's say this was a reminder :-)
From time to time I think I'm the only one looking at that file, and given that I don't find it useful (I still don't understand its role in our workflow), I will take care of reminding.

Stefano


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to