On Thu, Jul 9, 2009 at 2:20 PM, Robert Haasrobertmh...@gmail.com wrote:
On Jul 9, 2009, at 12:16 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Brendan Jurd dire...@gmail.com writes:
We're now about a week away from the start of the July 2009
commitfest, and we need to make a decision about whether
On Jul 9, 2009, at 12:35 PM, Brendan Jurd wrote:
We don't AFAIK collect data about these events. However, we could
have certain actions trigger the creation of an automated comment
(e.g., Status changed to Committed by petere) and let the
aforementioned comment view suffice for a history.
I think we might be better off just
leaving the closed commitfests up on the wiki, and putting a notice on
the app saying commitfests prior to July 2009 can be found at
wiki.postgresql.org.
+1. That's why we're switching technogies at the beginning of a dev cycle.
--
Josh Berkus
Brendan Jurd dire...@gmail.com writes:
We're now about a week away from the start of the July 2009
commitfest, and we need to make a decision about whether to start
using http://commitfest.postgresql.org to manage it, or punt to the
next commitfest and continue to use the wiki for July.
While
Em Thu, 09 Jul 2009 14:16:41 -0300, Tom Lane t...@sss.pgh.pa.us escreveu:
I'm not particularly wedded to the wiki page
history in terms of what it looks like or how it functions, but I do
feel a need to know what other people have done recently.
May be the new app could have a page with a
2009/7/10 Tom Lane t...@sss.pgh.pa.us:
While reorganizing my bookmarks for this I realized that there is a
fairly significant bit of functionality that's entirely missing from
the new app. With the wiki page, you could conveniently see what had
been done lately by examining the page history.
On Thu, Jul 09, 2009 at 02:35:04PM -0300, Dickson S. Guedes wrote:
This could help, maybe with a RSS in that (like in git).
+1 for the RSS feed, if only because I think it sounds neat :)
--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com
signature.asc
Description:
We don't AFAIK collect data about these events. However, we could
have certain actions trigger the creation of an automated comment
(e.g., Status changed to Committed by petere) and let the
aforementioned comment view suffice for a history.
Can you put in a simple event-recording trigger for
Josh Berkus j...@agliodbs.com writes:
We don't AFAIK collect data about these events. However, we could
have certain actions trigger the creation of an automated comment
(e.g., Status changed to Committed by petere) and let the
aforementioned comment view suffice for a history.
Can you put
On Jul 9, 2009, at 12:16 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Brendan Jurd dire...@gmail.com writes:
We're now about a week away from the start of the July 2009
commitfest, and we need to make a decision about whether to start
using http://commitfest.postgresql.org to manage it, or punt to
2009/7/10 Josh Berkus j...@agliodbs.com:
We don't AFAIK collect data about these events. However, we could
have certain actions trigger the creation of an automated comment
(e.g., Status changed to Committed by petere) and let the
aforementioned comment view suffice for a history.
Can you
Brendan Jurd dire...@gmail.com writes:
Bear in mind that CF activity over the past week has been in the realm
of 0-4 changes per 24 hours, so it's not like we are talking about
huge amounts of throughput here.
Well, it'll be more once commitfest actually starts, but in any case
it's not going
robertmh...@gmail.com (Robert Haas) writes:
I suspect both are true, but in the unlikely event that we decide on
some massive change to the system, we can either run the DBs in
parallel as Tom suggests, or dump out the older data in Wiki markup
and post it on there. But I can't imagine what
Brendan Jurd escribió:
Short answer: I could bring across the old commitfests but it would
take a couple hours at best per commitfest and result in little bits
of data loss here and there. I think we might be better off just
leaving the closed commitfests up on the wiki, and putting a notice
Hi folks,
We're now about a week away from the start of the July 2009
commitfest, and we need to make a decision about whether to start
using http://commitfest.postgresql.org to manage it, or punt to the
next commitfest and continue to use the wiki for July.
Robert and I have been upgrading the
Brendan Jurd dire...@gmail.com wrote:
If you think the app is fundamentally less useful than the wiki,
please say so and we'll work out whether we can resolve your
objection in time for the start of the CF.
It's been down for a while now. I don't know if this is causal, but
the failure
Brendan Jurd dire...@gmail.com wrote:
If you think the app is fundamentally less useful than the wiki,
please say so and we'll work out whether we can resolve your
objection in time for the start of the CF.
Oh, sure -- I post about it being down, and seconds after I hit send
it comes up
2009/7/8 Kevin Grittner kevin.gritt...@wicourts.gov:
Oh, sure -- I post about it being down, and seconds after I hit send
it comes up again. :-/
Do we know that cause?
Well, no, since I've never observed it being down and I really have
no idea what you mean by that.
Maybe you could
Brendan Jurd dire...@gmail.com wrote:
Maybe you could describe the symptoms you observed? Was the
webserver totally uncontactable, or was it an error in the web app
itself?
When I clicked the link to edit the comment, it clocked until the
browser timed out. So then I tried the URL for
On Tuesday 07 July 2009 11:29:07 Brendan Jurd wrote:
We're now about a week away from the start of the July 2009
commitfest, and we need to make a decision about whether to start
using http://commitfest.postgresql.org to manage it, or punt to the
next commitfest and continue to use the wiki
Peter Eisentraut pete...@gmx.net wrote:
in the future we might want to change from a fixed list of patch
sections to a free list of tags, say. Then someone might alter the
application backend, and we'd use that new version for the next
commit fest at the time. What will that do to the
Peter Eisentraut pete...@gmx.net writes:
With the wiki, the data of the old fests will pretty much stay what is
was, unless we change the wiki templates in drastic ways, as I
understand it. But if we did changes like the above, or more
complicated things, perhaps, what will happen? Perhaps
On Jul 7, 2009, at 2:14 PM, Peter Eisentraut pete...@gmx.net wrote:
On Tuesday 07 July 2009 11:29:07 Brendan Jurd wrote:
We're now about a week away from the start of the July 2009
commitfest, and we need to make a decision about whether to start
using http://commitfest.postgresql.org to
Robert Haas escribió:
I suspect both are true, but in the unlikely event that we decide on
some massive change to the system, we can either run the DBs in parallel
as Tom suggests, or dump out the older data in Wiki markup and post it on
there. But I can't imagine what we'd want to do
2009/7/8 Alvaro Herrera alvhe...@commandprompt.com:
By the way, if the migration of the current commitfest was an automatic
procedure, is there a chance that the old commitfests can be migrated as
well?
It wasn't really automatic as such. I used a few scripts that I saved
in case we needed
2009/7/8 Peter Eisentraut pete...@gmx.net:
I have the following concern: Likely, this tool and the overall process will
evolve over time. To pick an example that may or may not be actually useful,
in the future we might want to change from a fixed list of patch sections to a
free list of
2009/7/3 Robert Haas robertmh...@gmail.com:
The application stamps comments with the
community login of the person who left them, but the import stamped
them with names instead. This is actually of some significance, since
the app will allow you to edit your own comments but not those of
On Jul 3, 2009, at 11:56 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Jul 3, 2009 at 4:00 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
It seems to be inconsistent. Probably because everything wound up
Brendan Jurd dire...@gmail.com writes:
Please let us know if you encounter any problems with withe app, or
have suggestions for improvement.
It looks like every patch and comment is timestamped ... but with
yesterday (the time of data import, I suppose). This is much worse
than useless. If
On suggestions for improvement: I need to be able to bookmark the
commitfest summary list (whichever page is equivalent to the old wiki
page). The current URL seems to be
http://commitfest.postgresql.org/action/commitfest_view?id=2
which is both opaque as can be and not looking like it's intended
I tried the New Patch Comment feature. It's absolutely horrid.
I get a page showing a comment type button, one line for Message-ID,
and one line for Content. No explanation of what those are, and no
visibility any more of the patch I'm trying to comment on. I have no
idea what I'm supposed to
On Fri, Jul 3, 2009 at 10:35 AM, Tom Lanet...@sss.pgh.pa.us wrote:
On suggestions for improvement: I need to be able to bookmark the
commitfest summary list (whichever page is equivalent to the old wiki
page). The current URL seems to be
On Fri, Jul 3, 2009 at 10:40 AM, Tom Lanet...@sss.pgh.pa.us wrote:
I tried the New Patch Comment feature. It's absolutely horrid.
I get a page showing a comment type button, one line for Message-ID,
and one line for Content. No explanation of what those are, and no
visibility any more of the
Robert Haas wrote:
On Fri, Jul 3, 2009 at 10:35 AM, Tom Lanet...@sss.pgh.pa.us wrote:
On suggestions for improvement: I need to be able to bookmark the
commitfest summary list (whichever page is equivalent to the old wiki
page). The current URL seems to be
Robert Haas robertmh...@gmail.com writes:
On Fri, Jul 3, 2009 at 10:35 AM, Tom Lanet...@sss.pgh.pa.us wrote:
The current URL seems to be
http://commitfest.postgresql.org/action/commitfest_view?id=2
which is both opaque as can be and not looking like it's intended to
be stable over the long
Robert Haas robertmh...@gmail.com writes:
On Fri, Jul 3, 2009 at 10:40 AM, Tom Lanet...@sss.pgh.pa.us wrote:
I tried the New Patch Comment feature. It's absolutely horrid.
I get a page showing a comment type button, one line for Message-ID,
and one line for Content. No explanation of what
On Fri, Jul 3, 2009 at 11:46 AM, Heikki
Linnakangasheikki.linnakan...@enterprisedb.com wrote:
Robert Haas wrote:
On Fri, Jul 3, 2009 at 10:35 AM, Tom Lanet...@sss.pgh.pa.us wrote:
On suggestions for improvement: I need to be able to bookmark the
commitfest summary list (whichever page is
On Friday 03 July 2009 11:50:29 Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Jul 3, 2009 at 10:35 AM, Tom Lanet...@sss.pgh.pa.us wrote:
The current URL seems to be
http://commitfest.postgresql.org/action/commitfest_view?id=2
which is both opaque as can be and not
On Fri, 2009-07-03 at 14:06 -0400, Robert Treat wrote:
On Friday 03 July 2009 11:50:29 Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Jul 3, 2009 at 10:35 AM, Tom Lanet...@sss.pgh.pa.us wrote:
The current URL seems to be
On Fri, Jul 3, 2009 at 11:50 AM, Tom Lanet...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Jul 3, 2009 at 10:35 AM, Tom Lanet...@sss.pgh.pa.us wrote:
The current URL seems to be
http://commitfest.postgresql.org/action/commitfest_view?id=2
which is both opaque as can
On Fri, Jul 3, 2009 at 2:10 PM, Joshua D. Drakej...@commandprompt.com wrote:
O.k. I am probably blowing something out of the water here but do we
need yet another domain?
Because it's installed on a different VM and I don't want to move it
just to make the URL look different?
...Robert
--
Robert Treat wrote:
On Friday 03 July 2009 11:50:29 Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Jul 3, 2009 at 10:35 AM, Tom Lanet...@sss.pgh.pa.us wrote:
The current URL seems to be
http://commitfest.postgresql.org/action/commitfest_view?id=2
which is both opaque as can
On Fri, Jul 3, 2009 at 3:00 PM, Andrew Chernowa...@esilo.com wrote:
The current URL seems to be
http://commitfest.postgresql.org/action/commitfest_view?id=2
which is both opaque as can be and not looking like it's intended to
be stable over the long term.
I'm not sure why you would think
Hi,
Le 3 juil. 09 à 20:44, Robert Haas a écrit :
- Adding stable links with mnemonic names for the open, in progress,
and most recently closed commitfests.
May I suggest something looking about like:
http://commitfest.postgresql.org/current
http://commitfest.postgresql.org/open
I *am* using some kind of key. Specifically, in integer derived from
a serial column. It's just as stable as 16 random bytes displayed in
hex, but a lot shorter and easier to remember, if you're the sort of
person who likes to remember URLs. :-)
Wasn't aware of exately what you were doing.
On Fri, Jul 3, 2009 at 3:08 PM, Dimitri Fontainedfonta...@hi-media.com wrote:
Your software seems to be better than a wiki, but its potential users are
expressing needs and bikescheding. I think you'd better accept both kind of
changes as long as it's not making your life much harder than you'd
On Fri, Jul 3, 2009 at 3:15 PM, Andrew Chernowa...@esilo.com wrote:
I *am* using some kind of key. Specifically, in integer derived from
a serial column. It's just as stable as 16 random bytes displayed in
hex, but a lot shorter and easier to remember, if you're the sort of
person who likes
Robert Haas robertmh...@gmail.com writes:
Backing up for a moment to ten thousand feet here, I posted a link to
this web app on May 26th. I received several comments on it, all of
them positive, including some constructive feedback from you which I
took to heart. It is now July 1st, and I am
On Fri, Jul 3, 2009 at 3:27 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Backing up for a moment to ten thousand feet here, I posted a link to
this web app on May 26th. I received several comments on it, all of
them positive, including some constructive
Robert Haas robertmh...@gmail.com wrote:
I think it IS newest at the bottom, and I agree that that is how it
should be.
It seems to be inconsistent. Probably because everything wound up
with the same date, the order is probably more-or-less random. What
are the chances that the date or
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Robert Haas robertmh...@gmail.com wrote:
I think it IS newest at the bottom, and I agree that that is how it
should be.
It seems to be inconsistent. Probably because everything wound up
with the same date, the order is probably
Tom Lane t...@sss.pgh.pa.us wrote:
Currently, it seems that most or all of the entries are links to
archived messages. Scraping the date from the underlying message
would be the best thing.
Just for purposes of conversion, or as a long-term behavior?
-Kevin
--
Sent via pgsql-hackers
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Tom Lane t...@sss.pgh.pa.us wrote:
Currently, it seems that most or all of the entries are links to
archived messages. Scraping the date from the underlying message
would be the best thing.
Just for purposes of conversion, or as a
On Fri, Jul 3, 2009 at 3:40 PM, Robert Haasrobertmh...@gmail.com wrote:
I accept the need for and am willing to make the following changes:
- Changing the patch comment field from type text to type textarea and
integrating it into the patch view page to provide context.
- Adding a note to the
On Fri, Jul 3, 2009 at 4:00 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Robert Haas robertmh...@gmail.com wrote:
I think it IS newest at the bottom, and I agree that that is how it
should be.
It seems to be inconsistent. Probably because
2009/7/4 Robert Haas robertmh...@gmail.com:
On Fri, Jul 3, 2009 at 4:00 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
What
are the chances that the date or timestamp of the corresponding wiki
modification could be put onto the patch and comment
Robert Haas robertmh...@gmail.com writes:
On Fri, Jul 3, 2009 at 4:00 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
It seems to be inconsistent. Probably because everything wound up
with the same date, the order is probably more-or-less random.
2009/7/4 Tom Lane t...@sss.pgh.pa.us:
No, what we're complaining about is the ordering of comments for a
single patch.
Now moot, since I've successfully pulled the dates for all comments
with a message-id from the archives, and updated the database
accordingly.
Cheers,
BJ
--
Sent via
2009/7/3 Robert Haas robertmh...@gmail.com:
Also, we're currently missing the reviewer names
due to limitations of the import script; Brendan is fixing this.
Update: The reviewer names have now been populated.
Cheers,
BJ
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
On Fri, Jul 3, 2009 at 12:34 AM, Brendan Jurddire...@gmail.com wrote:
2009/7/3 Robert Haas robertmh...@gmail.com:
Also, we're currently missing the reviewer names
due to limitations of the import script; Brendan is fixing this.
Update: The reviewer names have now been populated.
looks
2009/7/3 Jaime Casanova jcasa...@systemguards.com.ec:
On Fri, Jul 3, 2009 at 12:34 AM, Brendan Jurddire...@gmail.com wrote:
2009/7/3 Robert Haas robertmh...@gmail.com:
Also, we're currently missing the reviewer names
due to limitations of the import script; Brendan is fixing this.
Update:
61 matches
Mail list logo
