Re: [Postgres-xc-developers] Code Merge with 8.4.4

[Mason S. <mas...@en...>]

If we do merge with 9.0, we still might want to merge in steps. to 8.4.4 
first, then 9.0 to more easily catch any problems and hopefully make the 
9.0 merge go more smoothly.

Unless we need any particular 9.0 feature, I am not in any hurry to 
merge until 9.0 has gone GA.  I like the idea of us working with a known 
stable base such that if we have a problem, we can be pretty sure it is 
in our code and not PostgreSQL. To be really paranoid, we could consider 
waiting until 9.0.1.

Thanks,

Mason


Koichi Suzuki wrote:
> Well, I think we should think more about merging to 9.0.
>
> ----------
> Koichi Suzuki
>
>
>
> 2010/5/26 Michael Paquier <mic...@gm...>:
>   
>> Hi,
>>
>> PostgreSQL 8.4.4 has been released on the 17th.
>> We didn't have any discussions about that yet, but it could be nice to do a
>> code merge.
>> Waiting for everybody's feedback.
>>
>> Regards,
>>
>> --
>> Michael Paquier
>> NIPPON TELEGRAPH AND
>> TELEPHONE CORPORATION
>> NTT Open Source Software Center
>>
>> ------------------------------------------------------------------------------
>>
>>
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>
>>
>>     
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>   


-- 
Mason Sharp
EnterpriseDB Corporation
The Enterprise Postgres Company


This e-mail message (and any attachment) is intended for the use of
the individual or entity to whom it is addressed. This message
contains information from EnterpriseDB Corporation that may be
privileged, confidential, or exempt from disclosure under applicable
law. If you are not the intended recipient or authorized to receive
this for the intended recipient, any use, dissemination, distribution,
retention, archiving, or copying of this communication is strictly
prohibited. If you have received this e-mail in error, please notify
the sender immediately by reply e-mail and delete this message.