On Tue, Sep 25, 2012 at 1:57 AM, Andrea Aime
<[email protected]>wrote:
> On Tue, Sep 25, 2012 at 12:23 AM, Mike Pumphrey <[email protected]> wrote:
>
>> Hi there. For the last few releases, I have been taking it upon myself
>> to accomplish two post-release actions that aren't actually part of the
>> official GeoServer release process:
>>
>> 1) Editing the welcome page of geoserver.org to add links to the
>> download and blog post:
>>
>> "September 21, 2012: _GeoServer 2.2_ released! _See what's new..._
>> http://geoserver.org/display/GEOS/Welcome
>>
>> 2) Loading the version specific docs on docs.geoserver.org and editing
>> the docs home page:
>>
>> http://docs.geoserver.org/
>> http://docs.geoserver.org/2.2.0/
>>
>> I see value in both of them, so my question is: should they be added as
>> steps to the release process, or should we stop bothering?
>>
>>
> Both valuable, should be added to the process and automated if at all
> possible
>
> Cheers
> Andrea
>
Is there a document describing the GeoServer release process? It seems
pretty ad hoc to me—and I'm the one that wrote the release announcement. :)
—R
--
Rolando Peñate
Product Manager
OpenGeo - http://opengeo.org/
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
