[Geoserver-devel] Summing up on road mapping

Andrea_Aime3 · September 18, 2009, 4:44pm

Hi,
in this mail I try to sum up all that we said about roadmapping
in the previous thread and try to propose something concrete.

Wiki wise, I see an organisation like the GSIP or releases
one, that is, hierarchical set of pages:
- a detail page per release
- a page containing ideas that still need resourcing (so, unscheduled)
- a page that links all previous releases
- a summary page containing a link to the previous releases page, the
future ideas page, and, inlined, the (two) pages for the two next
releases, the stable series one and the next major release one

Each release page should contain:
- a release theme (what we hope to achieve with that release)
- a tentative release date (and if the testing proposal goes on, the
   date in which the freeze begins and the testing team start hammering
   the nightlies)
- a summary of the changes that went in so far. This will be updated
   week by week and will result in the release summary that we
   always add to the release announcements
- a link to the open issues, sorted by priority
- a link to the issues closed thus far
- if the testing thing goes on, a summary of the things that need to
   be checked out the most (as a tool to direct the testing team)

Each week someone issues an update that summarizes what happened
during the previous week (by looking at the closed jiras) and
asks for update to the wiki page and release date, and also if
any developer is blocked waiting for someone else's feedback:
this should get people to actually answer the mail and as a
reminder for things that need our attention, it's unfortunately
easy to forget/overlook something in the daily storm of messages
we receive.

Do we want to try this out? Justin, Gabriel, David, Arne,
Simone, Alessio, Ben, Rob, Christian, Chris, Mark, Emanuele,
Francesco, Daniele, Rini, Mike and Alyssa,
and whoever else I forgot to list: yes, I'm looking at you!
Feedback welcomed, and then let's get down to business.

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

Francesco_Izzi1 · September 18, 2009, 6:15pm

Yes we try!
I thought, for all persons wishing to enter the testing team, a wiki page that suggests the test environment used: (JVM, operating systems, container, etc …)
It would be cool to test everything on different operating systems and various containers.
What do you think?

2009/9/18 Andrea Aime <aaime@anonymised.com>

Hi,
in this mail I try to sum up all that we said about roadmapping
in the previous thread and try to propose something concrete.

Wiki wise, I see an organisation like the GSIP or releases
one, that is, hierarchical set of pages:

a detail page per release

a page containing ideas that still need resourcing (so, unscheduled)

a page that links all previous releases

a summary page containing a link to the previous releases page, the
future ideas page, and, inlined, the (two) pages for the two next
releases, the stable series one and the next major release one

Each release page should contain:

a release theme (what we hope to achieve with that release)

a tentative release date (and if the testing proposal goes on, the
date in which the freeze begins and the testing team start hammering
the nightlies)

a summary of the changes that went in so far. This will be updated
week by week and will result in the release summary that we
always add to the release announcements

a link to the open issues, sorted by priority

a link to the issues closed thus far

if the testing thing goes on, a summary of the things that need to
be checked out the most (as a tool to direct the testing team)

Each week someone issues an update that summarizes what happened
during the previous week (by looking at the closed jiras) and
asks for update to the wiki page and release date, and also if
any developer is blocked waiting for someone else’s feedback:
this should get people to actually answer the mail and as a
reminder for things that need our attention, it’s unfortunately
easy to forget/overlook something in the daily storm of messages
we receive.

Do we want to try this out? Justin, Gabriel, David, Arne,
Simone, Alessio, Ben, Rob, Christian, Chris, Mark, Emanuele,
Francesco, Daniele, Rini, Mike and Alyssa,
and whoever else I forgot to list: yes, I’m looking at you!
Feedback welcomed, and then let’s get down to business.

Cheers
Andrea

–
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
Francesco Izzi
CNR - IMAA
geoSDI - NSDI
Responsabile Sviluppo Software

C.da S. Loja
85050 Tito Scalo - POTENZA (PZ)
Italia

phone: +39 0971427305
fax: +39 0971 427271
mob: +39 3402640314
mail: francesco.izzi@anonymised.com
skype: neofx8080

web: http://www.geosdi.org

Andrea_Aime3 · September 18, 2009, 6:25pm

Francesco Izzi ha scritto:

Yes we try!
I thought, for all persons wishing to enter the testing team, a wiki page that suggests the test environment used: (JVM, operating systems, container, etc ...)
It would be cool to test everything on different operating systems and various containers.
What do you think?

I think it would be great to have the widest variety possible,
because some bugs pop up only in selected environments.
Plus, I think we need the lowest entry barrier possible, so if someone
is using only, say, Glassfish, he should be able to keep on using that.
At the same time we need to put some limits, if some bug appears
only on FreeBSD + Jeronimo well, it might be no developer will be
able, or have time, to setup, reproduce and fix, so we should limit
the bug fixes we guarantee for regressions to a set of supported
platforms.

A page with a list of the testing team and the platform used by
each of them would be a good addition too, since it would show
what kind of variety we have.

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

Francesco_Izzi1 · September 18, 2009, 6:37pm

Yes Andrea, I meant just that.

I was thinking of a wiki page where mentioned supported platforms.

Cheers
Francesco

2009/9/18 Andrea Aime <aaime@anonymised.com1501…>

Francesco Izzi ha scritto:

Yes we try!
I thought, for all persons wishing to enter the testing team, a wiki page that suggests the test environment used: (JVM, operating systems, container, etc …)
It would be cool to test everything on different operating systems and various containers.
What do you think?

I think it would be great to have the widest variety possible,
because some bugs pop up only in selected environments.
Plus, I think we need the lowest entry barrier possible, so if someone
is using only, say, Glassfish, he should be able to keep on using that.
At the same time we need to put some limits, if some bug appears
only on FreeBSD + Jeronimo well, it might be no developer will be
able, or have time, to setup, reproduce and fix, so we should limit
the bug fixes we guarantee for regressions to a set of supported
platforms.

A page with a list of the testing team and the platform used by
each of them would be a good addition too, since it would show
what kind of variety we have.

Cheers
Andrea

–
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

–
Francesco Izzi
CNR - IMAA
geoSDI - NSDI
Responsabile Sviluppo Software

C.da S. Loja
85050 Tito Scalo - POTENZA (PZ)
Italia

phone: +39 0971427305
fax: +39 0971 427271
mob: +39 3402640314
mail: francesco.izzi@anonymised.com
skype: neofx8080

web: http://www.geosdi.org

jive · September 21, 2009, 8:50am

Hi Andrea; thanks for summing things up.

I am juggling a lot of things this week trying to get geotools out the door; in collaboration with the next geoserver. Can we *try* doing the wiki page now for this release and see how it goes?

At this late date I want to do something; you already have my feedback on the proposal and I would like to give it a go.

Jody

On 19/09/2009, at 2:44 AM, Andrea Aime wrote:

Hi,
in this mail I try to sum up all that we said about roadmapping
in the previous thread and try to propose something concrete.

Wiki wise, I see an organisation like the GSIP or releases
one, that is, hierarchical set of pages:
- a detail page per release
- a page containing ideas that still need resourcing (so, unscheduled)
- a page that links all previous releases
- a summary page containing a link to the previous releases page, the
  future ideas page, and, inlined, the (two) pages for the two next
  releases, the stable series one and the next major release one

Each release page should contain:
- a release theme (what we hope to achieve with that release)
- a tentative release date (and if the testing proposal goes on, the
  date in which the freeze begins and the testing team start hammering
  the nightlies)
- a summary of the changes that went in so far. This will be updated
  week by week and will result in the release summary that we
  always add to the release announcements
- a link to the open issues, sorted by priority
- a link to the issues closed thus far
- if the testing thing goes on, a summary of the things that need to
  be checked out the most (as a tool to direct the testing team)

Each week someone issues an update that summarizes what happened
during the previous week (by looking at the closed jiras) and
asks for update to the wiki page and release date, and also if
any developer is blocked waiting for someone else's feedback:
this should get people to actually answer the mail and as a
reminder for things that need our attention, it's unfortunately
easy to forget/overlook something in the daily storm of messages
we receive.

Do we want to try this out? Justin, Gabriel, David, Arne,
Simone, Alessio, Ben, Rob, Christian, Chris, Mark, Emanuele,
Francesco, Daniele, Rini, Mike and Alyssa,
and whoever else I forgot to list: yes, I'm looking at you!
Feedback welcomed, and then let's get down to business.

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Andrea_Aime3 · September 21, 2009, 5:13pm

Jody Garnett ha scritto:

Hi Andrea; thanks for summing things up.

I am juggling a lot of things this week trying to get geotools out the door; in collaboration with the next geoserver. Can we *try* doing the wiki page now for this release and see how it goes?

At this late date I want to do something; you already have my feedback on the proposal and I would like to give it a go.

Btw, Jody has been working on the page already and some mockup is here:
http://geoserver.org/display/GEOS/2.0-RC2

It looks nice to me.

Ah, about sending the weekly mail, how about having PSC members
taking turns on a monthly/release bases?
Someone drives the roadmap up until the release of, say, 1.7.7
or 2.0-RC2, then a volounteer steps in to replace him (so everyone
is free to step in once a month, and we avoid the "who does what"
and "oh, was this my week" dilemma that would occurr having people round
robin weekly)

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

Michael_Melvin · September 21, 2009, 7:25pm

I like that wiki page as well.

But what if no one volunteers for a release?

Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org

Andrea Aime wrote:

Jody Garnett ha scritto:

Hi Andrea; thanks for summing things up.

I am juggling a lot of things this week trying to get geotools out the door; in collaboration with the next geoserver. Can we *try* doing the wiki page now for this release and see how it goes?

At this late date I want to do something; you already have my feedback on the proposal and I would like to give it a go.

Btw, Jody has been working on the page already and some mockup is here:
http://geoserver.org/display/GEOS/2.0-RC2

It looks nice to me.

Ah, about sending the weekly mail, how about having PSC members
taking turns on a monthly/release bases?
Someone drives the roadmap up until the release of, say, 1.7.7
or 2.0-RC2, then a volounteer steps in to replace him (so everyone
is free to step in once a month, and we avoid the "who does what"
and "oh, was this my week" dilemma that would occurr having people round
robin weekly)

Cheers
Andrea

Andrea_Aime3 · September 21, 2009, 7:41pm

Mike Pumphrey ha scritto:

I like that wiki page as well.

But what if no one volunteers for a release?

Once in a while it might happen. If it happens
often we'll have no other choice but to reconsider
the way we do planning inside the PSC.
If the PSC cannot take a decision on that, well,
we always have the clause disbands a disfunctional
and returns all powers to TOPP (now OpenGEo):
http://geoserver.org/display/GEOSDOC/0+Project+Steering+Committee
(see the "dissolution of PSC")

So it seems we're setup to face even the darkest
day... hoping it will never come.

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

jive · September 21, 2009, 9:18pm

So Andrea is suggesting something like a release champion; to avoid passing things around. That may work - however to be honest the hard part here is filling in your own work that you are doing (and that happens regardless of if you are in charge of the release or not).

If we do lack a volunteer for a release - then no release happens. We have been leaning on Justin a lot to make things go after all.

Andrea was kind enough to fill in the blanks for that 2.0-RC2 page; do I need to talk to Mark to fill in the 1.7.7 page?

Jody

On 22/09/2009, at 5:25 AM, Mike Pumphrey wrote:

I like that wiki page as well.

But what if no one volunteers for a release?

Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org

Andrea Aime wrote:

Jody Garnett ha scritto:

Hi Andrea; thanks for summing things up.

I am juggling a lot of things this week trying to get geotools out the door; in collaboration with the next geoserver. Can we *try* doing the wiki page now for this release and see how it goes?

At this late date I want to do something; you already have my feedback on the proposal and I would like to give it a go.

Btw, Jody has been working on the page already and some mockup is here:
http://geoserver.org/display/GEOS/2.0-RC2
It looks nice to me.
Ah, about sending the weekly mail, how about having PSC members
taking turns on a monthly/release bases?
Someone drives the roadmap up until the release of, say, 1.7.7
or 2.0-RC2, then a volounteer steps in to replace him (so everyone
is free to step in once a month, and we avoid the "who does what"
and "oh, was this my week" dilemma that would occurr having people round
robin weekly)
Cheers
Andrea