Ok, so git upgrade is good to go and added a check for this issue. So...
dare i say... we should be ready to try again.
On Thu, Aug 2, 2012 at 7:36 AM, Justin Deoliveira wrote:
>
>
> On Wed, Aug 1, 2012 at 10:56 PM, wrote:
>
>> Hi Justin,
>>
>> ** **
>>
>> The revision number i used is from
On Wed, Aug 1, 2012 at 10:56 PM, wrote:
> Hi Justin,
>
> ** **
>
> The revision number i used is from the log output from cite wfs test
>
> ** **
>
>
> http://hudson.opengeo.org/hudson/view/cite/job/cite-wfs-1.1-master/547/consoleText
>
>
> ** **
>
> git revision = 6a230d54bdb01a8e38
On Thu, Aug 2, 2012 at 1:30 AM, Andrea Aime wrote:
> On Thu, Aug 2, 2012 at 6:56 AM, wrote:
>
>> Hi Justin,
>>
>> ** **
>>
>> The revision number i used is from the log output from cite wfs test
>>
>> ** **
>>
>>
>> http://hudson.opengeo.org/hudson/view/cite/job/cite-wfs-1.1-master/547/co
On Thu, Aug 2, 2012 at 6:56 AM, wrote:
> Hi Justin,
>
> ** **
>
> The revision number i used is from the log output from cite wfs test
>
> ** **
>
>
> http://hudson.opengeo.org/hudson/view/cite/job/cite-wfs-1.1-master/547/consoleText
>
>
> ** **
>
> git revision = 6a230d54bdb01a8e38c
Hi Justin,
The revision number i used is from the log output from cite wfs test
http://hudson.opengeo.org/hudson/view/cite/job/cite-wfs-1.1-master/547/consoleText
git revision = 6a230d54bdb01a8e38cf9eb056e5f61687acd4dd
git branch = 6a230d54bdb01a8e38cf9eb056e5f61687acd4dd
build date = 29-Jul-201
Ok, I think everything should be rolled back now... no permanent damage
done and we should be ready to try again. Perhaps it would be good to wait
until git upgraded on the server so we are able to do the final merge
during the publish step.
I will also have to add a check to the script that check
Victor, looking at the merge that occurred during this release I think
something is very wrong. I see you specified a revision of
"aacb7f76b710fc44a2938a69b163dd717bc818ec" for the release job, which is a
revision on the master branch, not the 8.x branch. The end result being a
release branch the w
