Re: Git migration timeline - Mailing list pgsql-hackers

On Mon, Aug 16, 2010 at 1:47 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I wrote:
>> Magnus Hagander <magnus@hagander.net> writes:
>>> According to the decision at the developer meeting, the migration to
>>> git should happen 17-20 Aug. Here's my proposed timeline. This will
>>> obviously affect development work some, and since the original
>>> timeline called for us having already released 9.0 buy then ;)
>
>> Core is currently talking about exactly when we want to push out
>> 9.0beta5 and/or 9.1alpha1, and the scheduling of the git transition has
>> to wait on that decision.  I don't think we're going to be ready for it
>> to begin on Tuesday.
>
> The current feeling among core seems to be that we should allow the git
> conversion to proceed according to Magnus' proposed schedule.  This
> would mean that we will *not* be able to wrap either a 9.0 update or
> 9.1alpha1 releases this week.  What we'd probably try to do instead is
> wrap 9.1alpha1 early next week, as the first attempt to generate
> tarballs from the git repository, and then wrap 9.0beta5 (or rc1) later
> in the week.  This slips the 9.0 schedule an extra week, but considering
> that nobody seems to be doing anything about the open 9.0 issues, that
> was likely to happen anyway.
>
> If anybody's really unhappy with this timeline, speak up now.

That sounds good, except for the part about nobody doing anything
about the 9.0 open issues.  Those issues are:

* Backup procedure is wrong? - Nobody's been able to clearly
articulate what the problem is, and according to Fujii Masao it's been
this way since 8.2.

* Walreceiver crashes in AIX - The person who originally reported this
problem has been slow to get back to us with the information needed to
figure out what is going on.  It would be helpful if someone else
could test to see if this a general problem with AIX, or something
specific to the reporter's installation.  Or if someone wants to
provide me with a login...

* BUG #5595: Documentation is not installs from VPATH build. - I'm not
sure this is really a release-blocker, but either way, I have been
assuming it's Peter's issue to fix.

* trace_recovery_messages inconsistency - This one seems like a simple
case of deciding what makes most sense, and doing it.  We should
definitely fix this before the wrap.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company