Re: [Geowebcache-devel] A 1.5.1 release

[Andrea A. <and...@ge...>]

On Tue, Jan 14, 2014 at 6:27 PM, Kevin Smith <ks...@bo...>wrote:

> Sorry, gmail decided to spontaneously send before I had finished writing
> that email.
>

Ah, these evolution of artificial intelligence worry me...


>
>
> On 14 January 2014 09:16, Kevin Smith <ks...@bo...> wrote:
>
>>
>>
>>
>> On 14 January 2014 01:02, Andrea Aime <and...@ge...>wrote:
>>
>>>
>>> I hope so, I've tried to make it a clean refactor, basically just moved
>>> the request cascading code back in WMSLayer while
>>> making the operation pluggable, and added a test for it that was not
>>> there before (request cascading was not tested at all).
>>> Finally, did some interactive testing in the stand alone version to make
>>> sure it's working as expected.
>>>
>>> So.. any feedback? Should I prepare a pull request against the 1.5.x
>>> branch?
>>>  Also, were all the fixes ported to the 1.5.x branch, if so, we could
>>> release from it no?
>>>
>>
>> The fixes for the BDB Disk Quota store not setting up its version
>> tracking file (#202) and for GetCapabilitiesConfiguration being broken and
>> having out of date documentation (#196) have been backported to 1.5.x  the
>> other changes are only on master at the moment.
>>
>
> Whatever gets released this weekend, I'd really like to get everything
> that made it into master to go out rather than having to wait another 6
> months.  Whether that means backporting all of it to 1.5.x, calling master
> 1.5.1 and branching a new master for 1.6, or doing 1.5.1 and 1.6-beta
> together.
>

Whatever is less work works for me... do we have many commits to
cherry-pick on 1.5.x?
Otherwise calling master 1.5.x and the current 1.5.x something like 1.5.0.x
would be quick enough.


>
> I've only had a chance to give a quick look at the proxy layer patch, but
> it seems OK  for backporting to me.
>

Nice. Can I merge? :-)


>
>>
>>>
>>>>
>>>> Regardless of what's done, I'll be moving this weekend so I'm probably
>>>> not going to have time to to do a release (and certainly not 2 of them if
>>>> we do both 1.5.1 and 1.6-beta together)
>>>>
>>>
>>> I may be able to help. What's the release procedure?
>>>
>>
>>
> The release procedure is in RELEASE_NOTES.txt.
>

Is it?
https://github.com/GeoWebCache/geowebcache/blob/master/RELEASE_NOTES.txt
To me that looks like a changelog :-)


> I think it uses the same credentials to push the finished artifacts to the
> maven repository as for a GeoServer release. The web page has moved to a
> new server since I did the 1.4.0 release, I think Justin knows the
> credentials for logging in.
>

Justin, is that something that can be done from outside Boundless?

Cheers
Andrea


-- 
== Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information ==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------