Bruce Momjian wrote:
I would like other developers to add/modify the todo list. The
master is the text file, and I generate the HTML so the web team can
pull the HTML for our web site. If you modify just the text file, I
will see the commit and update the HTML, and if you want my scripts,
I
On Sun, 2005-12-11 at 23:54 -0500, Bruce Momjian wrote:
If I am wrong, please someone tell me why I am wrong. Don't way we
would like to have X too as well as what we already have, but not supply
any more manpower. You might as well say you want to live forever, but
not give any way of
Peter Eisentraut wrote:
Bruce Momjian wrote:
I would like other developers to add/modify the todo list. The
master is the text file, and I generate the HTML so the web team can
pull the HTML for our web site. If you modify just the text file, I
will see the commit and update the HTML,
On Sat, 2005-12-10 at 21:16 -0500, Bruce Momjian wrote:
Not sure what else can be done to improve this process.
I think the barrier to adding new TODO entries or modifying existing
ones is too high. While it's great that Bruce maintains the list, the
inevitable result is that the list tends to
Bruce Momjian wrote:
Well, the item was added at the request of Peter Eisentraut and
Martijn van Oosterhout and took place on hackers. The TODO addition
was posted too:
http://archives.postgresql.org/pgsql-hackers/2005-12/msg00333.php
The discussion did not mention anything about
Neil Conway [EMAIL PROTECTED] writes:
On Sat, 2005-12-10 at 21:16 -0500, Bruce Momjian wrote:
Not sure what else can be done to improve this process.
Why is the TODO list keep in the source code repository, anyway? One
alternative would be to move it to a wiki.
That seems unlikely to improve
On Mon, 2005-12-12 at 09:39 +0800, Christopher Kings-Lynne wrote:
Call me crazy - but isn't this what you usually use a bug tracker for?
Well, some people do. I don't really see the point, though. What
advantages would it have?
-Neil
---(end of
Neil Conway wrote:
I agree, but I think this is another symptom of having only one person
maintain the list. It is a non-trivial amount of work to understand all
the arguments in a complex -hackers thread and distill that into a few
accurate sentences that summarize the consensus (if there
Joshua D. Drake wrote:
Why is the TODO list keep in the source code repository, anyway? One
alternative would be to move it to a wiki. That would allow other people
to contribute to maintaining the list, with less procedural overhead.
The GCC folks do this, for example: example:
It would also be useful to see who has signed on as the lead or to work on
a particular subproject in case other developers would like to either lead
or help a lead on the project.
I would request a vote interface but I think we would get to many
mysqlisms ;)
You are dreaming on this one.
Joshua D. Drake wrote:
It would also be useful to see who has signed on as the lead or to work on
a particular subproject in case other developers would like to either lead
or help a lead on the project.
I would request a vote interface but I think we would get to many
mysqlisms ;)
Joshua D. Drake wrote:
I guess I just don't understand why so many other projects larger
then us and much smaller then us can do it, but we can't.
Perhaps it is a question of project culture. As I see PostgreSQL
development, there is no such thing as a roadmap or an agreed plan, what
the
I've written a small patch for following TODO item:
«Add GUC variable to run a command on database
panic or smart/fast/immediate shutdown.»
It adds two GUC variables as:
enable_atexit_script_file
atexit_script_file
postmaster will run related script file with passing shutdown type
(like
Volkan YAZICI [EMAIL PROTECTED] writes:
I've written a small patch for following TODO item:
«Add GUC variable to run a command on database
panic or smart/fast/immediate shutdown.»
I'm not sure why this is in TODO; it's a stupid if not outright
dangerous idea. Quite aside from any security
Andrew Dunstan [EMAIL PROTECTED] writes:
This is what bothers me about having such an informal TODO list. There is a
danger that people will work in items only to have them shot down, which is
a great way to turn off developers. And there is also a danger that other
people will think that the
On 12/10/05, Tom Lane [EMAIL PROTECTED] wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
This is what bothers me about having such an informal TODO list. There is
a
danger that people will work in items only to have them shot down, which
is
a great way to turn off developers. And there is
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
This is what bothers me about having such an informal TODO list. There is a
danger that people will work in items only to have them shot down, which is
a great way to turn off developers. And there is also a danger that other
people
Jaime Casanova wrote:
On 12/10/05, Tom Lane [EMAIL PROTECTED] wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
This is what bothers me about having such an informal TODO list. There is
a
danger that people will work in items only to have them shot down, which
is
a great way to turn
18 matches
Mail list logo
