New CF app deployment
Hi!
Last I said something about the new CF app I said I was planning to deploy
it over the holidays, and that clearly did not happen.
But I've been talking to Michael, as the current cf-chief, and doing some
further testing with it, and we think now is a good time to go for it :) As
the plan is to close out the current CF just a few days from now, we're
going to use that and try to swap it out when traffic is at least at it's
lowest (even if we're well aware it's not going to be zero).
So based on this, we plan to:
In the late evening on Jan 19th (evening European time that is), I will
make the current CF app readonly, and move it to a new url where it will
remain available for the foreseeable future (we have a lot of useful data
in it after all).
Once this is done, Michael (primarily) will start working on syncing up the
information about the latest patches into the new app. Much info is already
synced there, but to make sure all the latest changes are included.
In the morning European time on the 20th, I'll take over and try to finish
up what's left. And sometime during the day when things are properly in
sync, we'll open up the new app for business to all users.
There are surely some bugs remaining in the system, so please have some
oversight with that over the coming days/weeks. I'll try to get onto fixing
them as soon as I can - and some others can look at that as well if it's
something critical at least.
Further status updates to come as we start working on it...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
On Tue, Jan 13, 2015 at 2:35 PM, Magnus Hagander <magnus@hagander.net> wrote:
Further status updates to come as we start working on it...
Things are looking good so far. All the information has been synced up
between both apps for the current CF and the next one. One the switch
is done, I would recommend to each patch author and reviewer to check
the patches they are registered on, and do the necessary modifications
if we missed something. Error is human.
Note as well that the new CF app has a couple of differences with the
old app regarding the patch status:
- When a patch is marked as "returned with feedback", it is
automatically added to the next CF
- When a patch is marked as "rejected", it is *not* added in the next
CF, but you can still re-add a new entry manually in the next app.
So "rejected" means as well that a patch is marked as such because the
author does not have time/resources to work on it for the next CF(s).
Thanks,
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Mon, Jan 19, 2015 at 3:16 AM, Michael Paquier <michael.paquier@gmail.com>
wrote:
On Tue, Jan 13, 2015 at 2:35 PM, Magnus Hagander <magnus@hagander.net>
wrote:Further status updates to come as we start working on it...
Things are looking good so far. All the information has been synced up
between both apps for the current CF and the next one. One the switch
is done, I would recommend to each patch author and reviewer to check
the patches they are registered on, and do the necessary modifications
if we missed something. Error is human.Note as well that the new CF app has a couple of differences with the
old app regarding the patch status:
- When a patch is marked as "returned with feedback", it is
automatically added to the next CF
- When a patch is marked as "rejected", it is *not* added in the next
CF, but you can still re-add a new entry manually in the next app.
So "rejected" means as well that a patch is marked as such because the
author does not have time/resources to work on it for the next CF(s).
Thanks,
The new site has been deployed and should now be usable.
The old site is still available in readonly mode at
https://commitfest-old.postgresql.org/.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
On Mon, Jan 19, 2015 at 3:57 PM, Magnus Hagander <magnus@hagander.net> wrote:
The new site has been deployed and should now be usable.
The old site is still available in readonly mode at
https://commitfest-old.postgresql.org/.
These links, which were originally requested by Tom and which I have
bookmarked, used, and publicized extensively, no longer work:
https://commitfest.postgresql.org/action/commitfest_view/inprogress
https://commitfest.postgresql.org/action/commitfest_view/open
Any chance you could make those work, or at the very least provide
some equivalent?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Mon, Jan 19, 2015 at 10:01 PM, Robert Haas <robertmhaas@gmail.com> wrote:
On Mon, Jan 19, 2015 at 3:57 PM, Magnus Hagander <magnus@hagander.net>
wrote:The new site has been deployed and should now be usable.
The old site is still available in readonly mode at
https://commitfest-old.postgresql.org/.These links, which were originally requested by Tom and which I have
bookmarked, used, and publicized extensively, no longer work:https://commitfest.postgresql.org/action/commitfest_view/inprogress
https://commitfest.postgresql.org/action/commitfest_view/openAny chance you could make those work, or at the very least provide
some equivalent?
Hmm. I missed that request.
Will fix.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
On Mon, Jan 19, 2015 at 3:57 PM, Magnus Hagander <magnus@hagander.net> wrote:
The new site has been deployed and should now be usable.
There are, for some reason, three copies of "Clarify need for memory
barriers in bgworkers" in the in-progress CF. I don't know why that
happened, or how to fix it.
Also, the old app did this:
Status Summary. Needs Review: 34, Waiting on Author: 6, Ready for
Committer: 5, Committed: 16, Returned with Feedback: 12, Rejected: 5.
Total: 78.
...and you could click on the statuses to filter by that status. I
see that this new app has a different way to filter by status, which
is fine, but I though the quick summary at the top was awfully useful,
so you could see how many total patches there were and how much
progress we were making.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Mon, Jan 19, 2015 at 4:05 PM, Robert Haas <robertmhaas@gmail.com> wrote:
On Mon, Jan 19, 2015 at 3:57 PM, Magnus Hagander <magnus@hagander.net> wrote:
The new site has been deployed and should now be usable.
There are, for some reason, three copies of "Clarify need for memory
barriers in bgworkers" in the in-progress CF. I don't know why that
happened, or how to fix it.
There are also two copies of "ctidscan as an example of custom-scan".
Also, I can't figure out what I'm supposed to do with the "Author" and
"Reviewer" checkboxes. Checking and unchecking them doesn't seem to
do anything.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Mon, Jan 19, 2015 at 10:03 PM, Magnus Hagander <magnus@hagander.net>
wrote:
On Mon, Jan 19, 2015 at 10:01 PM, Robert Haas <robertmhaas@gmail.com>
wrote:On Mon, Jan 19, 2015 at 3:57 PM, Magnus Hagander <magnus@hagander.net>
wrote:The new site has been deployed and should now be usable.
The old site is still available in readonly mode at
https://commitfest-old.postgresql.org/.These links, which were originally requested by Tom and which I have
bookmarked, used, and publicized extensively, no longer work:https://commitfest.postgresql.org/action/commitfest_view/inprogress
https://commitfest.postgresql.org/action/commitfest_view/openAny chance you could make those work, or at the very least provide
some equivalent?Hmm. I missed that request.
Will fix.
Fixed. Those were easy :)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
On Mon, Jan 19, 2015 at 10:05 PM, Robert Haas <robertmhaas@gmail.com> wrote:
On Mon, Jan 19, 2015 at 3:57 PM, Magnus Hagander <magnus@hagander.net>
wrote:The new site has been deployed and should now be usable.
There are, for some reason, three copies of "Clarify need for memory
barriers in bgworkers" in the in-progress CF. I don't know why that
happened, or how to fix it.Also, the old app did this:
Status Summary. Needs Review: 34, Waiting on Author: 6, Ready for
Committer: 5, Committed: 16, Returned with Feedback: 12, Rejected: 5.
Total: 78....and you could click on the statuses to filter by that status. I
see that this new app has a different way to filter by status, which
is fine, but I though the quick summary at the top was awfully useful,
so you could see how many total patches there were and how much
progress we were making.
I'll add that to my TODO - but it won't be fixed tonight.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
On Mon, Jan 19, 2015 at 10:10 PM, Robert Haas <robertmhaas@gmail.com> wrote:
On Mon, Jan 19, 2015 at 4:05 PM, Robert Haas <robertmhaas@gmail.com>
wrote:On Mon, Jan 19, 2015 at 3:57 PM, Magnus Hagander <magnus@hagander.net>
wrote:
The new site has been deployed and should now be usable.
There are, for some reason, three copies of "Clarify need for memory
barriers in bgworkers" in the in-progress CF. I don't know why that
happened, or how to fix it.There are also two copies of "ctidscan as an example of custom-scan".
Yeah, Michael pointed out he was unable to fix that one. I think I've fixed
the permissions errors required for that, so I'll wait for him to try again
to confirm that I managed to fix it.
Also, I can't figure out what I'm supposed to do with the "Author" and
"Reviewer" checkboxes. Checking and unchecking them doesn't seem to
do anything.
That's part of the "mass email to reviewers/authors" that's available only
to cf managers (which you are flagged as in the system). There's a button
to actually send the mail at the bottom (pick "selected" as receipient).
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
On Tue, Jan 20, 2015 at 6:54 AM, Magnus Hagander <magnus@hagander.net> wrote:
On Mon, Jan 19, 2015 at 10:10 PM, Robert Haas <robertmhaas@gmail.com> wrote:
On Mon, Jan 19, 2015 at 4:05 PM, Robert Haas <robertmhaas@gmail.com>
wrote:On Mon, Jan 19, 2015 at 3:57 PM, Magnus Hagander <magnus@hagander.net>
wrote:The new site has been deployed and should now be usable.
There are, for some reason, three copies of "Clarify need for memory
barriers in bgworkers" in the in-progress CF. I don't know why that
happened, or how to fix it.There are also two copies of "ctidscan as an example of custom-scan".
Yeah, Michael pointed out he was unable to fix that one. I think I've fixed
the permissions errors required for that, so I'll wait for him to try again
to confirm that I managed to fix it.
Thanks for fixing the permission problem. I have removed the
duplicated entries, something actually caused by me when adding the
existing patches to the new app.
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Hello, the new app's clean looking gets my favor and the
integrated operation will do good for me:)
By the way, I got the following notice when I tried to "Add
comment" on the new app.
"Note!: This form will generate an email to the public
mailinglist pgsql-hackers, with sender set to
horiguchi.kyotaro@oss.ntt.co.jp!"
Hmm. The mail address indeed *was* mine but is now obsolete, so
that the email might bounce. But I haven't find how to change it
within the app itself, and the PostgreSQL community account page.
https://www.postgresql.org/account/
Could you tell me how do I change the sender address?
regards,
--
Kyotaro Horiguchi
NTT Open Source Software Center
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Hi,
On 2015-01-19 21:57:20 +0100, Magnus Hagander wrote:
The new site has been deployed and should now be usable.
I think this unfortunately lost the RSS feature? I found that quite
useful to see who changed what recently (it's forwared to an imap
mailbox for me...).
What I'm also missing from the old app is that previously 'reviews'
could explicitly be linked from the app. Now there's a list of emails in
the thread, nice!, but in bigger threads that really doesn't help to
find the actual review.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, Jan 20, 2015 at 10:09 AM, Andres Freund <andres@2ndquadrant.com> wrote:
Hi,
On 2015-01-19 21:57:20 +0100, Magnus Hagander wrote:
The new site has been deployed and should now be usable.
I think this unfortunately lost the RSS feature? I found that quite
useful to see who changed what recently (it's forwared to an imap
mailbox for me...).
Yep, added here:
https://commitfest.postgresql.org/3/109/
I linked it with 20140922230255.GD2521@awork2.anarazel.de. I also
recall that you and Robert were marked as reviewers, right?
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 2015-01-20 11:05:43 +0900, Michael Paquier wrote:
On Tue, Jan 20, 2015 at 10:09 AM, Andres Freund <andres@2ndquadrant.com> wrote:
Hi,
On 2015-01-19 21:57:20 +0100, Magnus Hagander wrote:
The new site has been deployed and should now be usable.
I think this unfortunately lost the RSS feature? I found that quite
useful to see who changed what recently (it's forwared to an imap
mailbox for me...).Yep, added here:
https://commitfest.postgresql.org/3/109/
I linked it with 20140922230255.GD2521@awork2.anarazel.de. I also
recall that you and Robert were marked as reviewers, right?
I think you misunderstood me ;). I was talking about the old CF
application providing a RSS feed of all changes to all entries.
I.e.
https://commitfest-old.postgresql.org/action/commitfest_activity.rss
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, Jan 20, 2015 at 4:31 PM, Andres Freund <andres@2ndquadrant.com> wrote:
On 2015-01-20 11:05:43 +0900, Michael Paquier wrote:
On Tue, Jan 20, 2015 at 10:09 AM, Andres Freund <andres@2ndquadrant.com> wrote:
Hi,
On 2015-01-19 21:57:20 +0100, Magnus Hagander wrote:
The new site has been deployed and should now be usable.
I think this unfortunately lost the RSS feature? I found that quite
useful to see who changed what recently (it's forwared to an imap
mailbox for me...).Yep, added here:
https://commitfest.postgresql.org/3/109/
I linked it with 20140922230255.GD2521@awork2.anarazel.de. I also
recall that you and Robert were marked as reviewers, right?I think you misunderstood me ;). I was talking about the old CF
application providing a RSS feed of all changes to all entries.I.e.
https://commitfest-old.postgresql.org/action/commitfest_activity.rss
Oh, I didn't know this one. That's indeed useful.
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
"Kyotaro" == Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp> writes:
Kyotaro> Hmm. The mail address indeed *was* mine but is now obsolete,
Kyotaro> so that the email might bounce. But I haven't find how to
Kyotaro> change it within the app itself, and the PostgreSQL community
Kyotaro> account page.
Just being able to change the email address on the community account
isn't enough; I for one am subscribed to the lists with a different
email address than the one associated with my community account (for
spam management reasons). There needs to be a way to have multiple
addresses or to specify which is to be used for the post.
--
Andrew (irc:RhodiumToad)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Michael Paquier <michael.paquier@gmail.com> writes:
On Tue, Jan 20, 2015 at 4:31 PM, Andres Freund <andres@2ndquadrant.com> wrote:
I think you misunderstood me ;). I was talking about the old CF
application providing a RSS feed of all changes to all entries.
https://commitfest-old.postgresql.org/action/commitfest_activity.rss
Oh, I didn't know this one. That's indeed useful.
Personally, I never used the RSS feed as such, but I did often consult the
"activity log" pages, which I think are equivalent:
https://commitfest-old.postgresql.org/action/commitfest_activity?id=25
That feature seems to be gone too :-(
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, Jan 20, 2015 at 3:43 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Michael Paquier <michael.paquier@gmail.com> writes:
On Tue, Jan 20, 2015 at 4:31 PM, Andres Freund <andres@2ndquadrant.com>
wrote:
I think you misunderstood me ;). I was talking about the old CF
application providing a RSS feed of all changes to all entries.
https://commitfest-old.postgresql.org/action/commitfest_activity.rssOh, I didn't know this one. That's indeed useful.
Personally, I never used the RSS feed as such, but I did often consult the
"activity log" pages, which I think are equivalent:https://commitfest-old.postgresql.org/action/commitfest_activity?id=25
That feature seems to be gone too :-(
Yeah, that's annoying.
In fact, I'm the one who forced the RSS feed into the old system, and it's
something I use all the time myself. Oops.
Turns out I have those in a feature branch that it appears I forgot to
merge :( And it also no longer merges cleanly.
I've added this to my short-term TODO, and will look at it this evening.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
Hi
I cannot to set my name as author for patch:
https://commitfest.postgresql.org/4/112/
Regards
Pavel
2015-01-13 6:35 GMT+01:00 Magnus Hagander <magnus@hagander.net>:
Show quoted text
Hi!
Last I said something about the new CF app I said I was planning to deploy
it over the holidays, and that clearly did not happen.But I've been talking to Michael, as the current cf-chief, and doing some
further testing with it, and we think now is a good time to go for it :) As
the plan is to close out the current CF just a few days from now, we're
going to use that and try to swap it out when traffic is at least at it's
lowest (even if we're well aware it's not going to be zero).So based on this, we plan to:
In the late evening on Jan 19th (evening European time that is), I will
make the current CF app readonly, and move it to a new url where it will
remain available for the foreseeable future (we have a lot of useful data
in it after all).Once this is done, Michael (primarily) will start working on syncing up
the information about the latest patches into the new app. Much info is
already synced there, but to make sure all the latest changes are included.In the morning European time on the 20th, I'll take over and try to finish
up what's left. And sometime during the day when things are properly in
sync, we'll open up the new app for business to all users.There are surely some bugs remaining in the system, so please have some
oversight with that over the coming days/weeks. I'll try to get onto fixing
them as soon as I can - and some others can look at that as well if it's
something critical at least.Further status updates to come as we start working on it...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
