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?
I note that 2) as it currently stands requires access to an OpenGeo server, as that's where these docs are hosted.
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org
- 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?
I note that 2) as it currently stands requires access to an OpenGeo server, as that’s where these docs are hosted.
Could we move these to github pages? They essentially do free hosting of static content.
Thanks,
Mike Pumphrey
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
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
On Tue, Sep 25, 2012 at 12:23 AM, Mike Pumphrey <mike@anonymised.com> 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:
- 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
- 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
–
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
On Tue, Sep 25, 2012 at 1:57 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:
On Tue, Sep 25, 2012 at 12:23 AM, Mike Pumphrey <mike@anonymised.com> 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:
- 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
- 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/
Yeah, confluence has a rest api but we can’t turn it on at the moment because our instance is so old and upgrading is a pain.
Github pages could work. It looks like adding new content is as easy as just making a commit (to a “special branch” in the repository). This could be pretty easily added to the release process publish step.
On Mon, Sep 24, 2012 at 11:57 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:
On Tue, Sep 25, 2012 at 12:23 AM, Mike Pumphrey <mike@anonymised.com> 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:
- 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
- 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
–
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
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
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
http://docs.geoserver.org/stable/en/developer/release-guide/index.html
On Tue, Sep 25, 2012 at 10:54 AM, Rolando Peñate <rpenate@anonymised.com> wrote:
On Tue, Sep 25, 2012 at 1:57 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:
On Tue, Sep 25, 2012 at 12:23 AM, Mike Pumphrey <mike@anonymised.com> 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:
- 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
- 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
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Btw, I note that the release schedule on http://docs.geoserver.org/stable/en/developer/release-schedule/index.html#release-cycle is pretty far off the mark. Do we need to adjust the schedule? Seems like keeping it in PNG format is probably not good for maintainability.
If that graphic is only meant to illustrative, maybe it would make sense to redo it without any actual dates on it.
–
David Winslow
OpenGeo - http://opengeo.org/
On Tue, Sep 25, 2012 at 11:27 AM, David Winslow <dwinslow@anonymised.com> wrote:
http://docs.geoserver.org/stable/en/developer/release-guide/index.html
On Tue, Sep 25, 2012 at 10:54 AM, Rolando Peñate <rpenate@anonymised.com> wrote:
On Tue, Sep 25, 2012 at 1:57 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:
On Tue, Sep 25, 2012 at 12:23 AM, Mike Pumphrey <mike@anonymised.com> 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:
- 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
- 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
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
On Tue, Sep 25, 2012 at 5:32 PM, David Winslow <dwinslow@anonymised.com> wrote:
Btw, I note that the release schedule on http://docs.geoserver.org/stable/en/developer/release-schedule/index.html#release-cycle is pretty far off the mark. Do we need to adjust the schedule? Seems like keeping it in PNG format is probably not good for maintainability.
If that graphic is only meant to illustrative, maybe it would make sense to redo it without any actual dates on it.
It is indeed only illustrative
Cheers
Andrea
–
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
Hi guys. I still have this thread as an outstanding todo in my inbox, so trying to move it forward.
Sounds like the action items as discussed in this thread (with suggested assignees) are:
* Research/implement GitHub pages for our (versioned) documentation (Justin?)
* Edit the release process to add posting of GitHub pages (Justin/Mike?)
* Redo release schedule graphic to be illustrative and not as specific (Rollie?)
* Edit the release process to add updating geoserver.org with latest version info (Mike?)
Did I miss anything? I'll make JIRA tickets for these unless others have anything to add.
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org
On 9/25/2012 8:05 AM, Justin Deoliveira wrote:
Yeah, confluence has a rest api but we can't turn it on at the moment
because our instance is so old and upgrading is a pain.
Github pages could work. It looks like adding new content is as easy as
just making a commit (to a "special branch" in the repository). This could
be pretty easily added to the release process publish step.
On Mon, Sep 24, 2012 at 11:57 PM, Andrea Aime
<andrea.aime@anonymised.com>wrote:
On Tue, Sep 25, 2012 at 12:23 AM, Mike Pumphrey <mike@anonymised.com> 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
--
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
-------------------------------------------------------
------------------------------------------------------------------------------
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
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
In support of the 2.2.1 release (woo!), I went ahead and added the two steps I've been taking care of to the Release Guide, and took care of them for this release.
See https://github.com/geoserver/geoserver/pull/47
Still hoping we can find a better solution for hosting our version specific docs, but that can come in time.
Thanks to Justin for pulling me out of Git Hell, as always.
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org
On 10/15/2012 10:08 AM, Mike Pumphrey wrote:
Hi guys. I still have this thread as an outstanding todo in my inbox, so trying to move it forward.
Sounds like the action items as discussed in this thread (with suggested assignees) are:
* Research/implement GitHub pages for our (versioned) documentation (Justin?)
* Edit the release process to add posting of GitHub pages (Justin/Mike?)
* Redo release schedule graphic to be illustrative and not as specific (Rollie?)
* Edit the release process to add updating geoserver.org with latest version info (Mike?)
Did I miss anything? I'll make JIRA tickets for these unless others have anything to add.
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org
On 9/25/2012 8:05 AM, Justin Deoliveira wrote:
Yeah, confluence has a rest api but we can't turn it on at the moment
because our instance is so old and upgrading is a pain.
Github pages could work. It looks like adding new content is as easy as
just making a commit (to a "special branch" in the repository). This could
be pretty easily added to the release process publish step.
On Mon, Sep 24, 2012 at 11:57 PM, Andrea Aime
<andrea.aime@anonymised.com>wrote:
On Tue, Sep 25, 2012 at 12:23 AM, Mike Pumphrey <mike@anonymised.com> 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
--
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
-------------------------------------------------------
------------------------------------------------------------------------------
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
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel