Hello developers and PSC members,
GSIP 5 has been up for a little while now and I think it is time to wrap it up and call a vote on it.
You can find it here: http://docs.codehaus.org/display/GEOS/GSIP+5+-+Release+process
I will let people look over it for the next few days and maybe send out for a vote on tuesday.
Feel free to post more comments on the page or in email.
--
Brent Owens
(The Open Planning Project)
Thanks Brent,
Checking over the wiki page:
- http://docs.codehaus.org/display/GEOS/GSIP+5+-+Release+process
A couple corrections:
- in the discussion of schedule you mention the PSC members making a release, that is not part of the PSC mandate (sorry).
- we need to record where the schedule is maintained, in the past I have been told to use the Jira roadmap, (added the link to the page)
- the "work" of accepting this change is to update the policies and procedures pages (I have linked to them on the wiki page)
Thanks for documenting the discussion about using SNAPSHOT GeoTools releases, I will try and get a page up on how to publish a GeoTools SNAPSHOT to the m2 repository as part of their developers guide.
Check points:
- need to highlight the conversation threads on "nable" to agree with other proposals?
Cheers,
Jody
Hello developers and PSC members,
GSIP 5 has been up for a little while now and I think it is time to wrap it up and call a vote on it.
You can find it here: http://docs.codehaus.org/display/GEOS/GSIP+5+-+Release+processI will let people look over it for the next few days and maybe send out for a vote on tuesday.
Feel free to post more comments on the page or in email.
Brent Owens ha scritto:
Hello developers and PSC members,
GSIP 5 has been up for a little while now and I think it is time to wrap it up and call a vote on it.
You can find it here: http://docs.codehaus.org/display/GEOS/GSIP+5+-+Release+processI will let people look over it for the next few days and maybe send out for a vote on tuesday.
Feel free to post more comments on the page or in email.
Here we go:
* release scheduling: sifficient -> sufficient
* release scheduling: once per month for the main development branches.
Hem, I agree from trunk, but what if a branch like 1.4.x did not
accumulate any interesting change?
That's all, for the rest it's perfectly ok to me.
Cheers
Andrea
Spelling:
- my speling sucks 
Releases once a month:
- I think GeoServer, overall, should have at least one release a month. If not more frequently. It shows that the project is very active and it also helps spreading the word of its existence.
- Also, we usually manage a release every month or so anyways, even with not many fixes or changes
Brent Owens
(The Open Planning Project)
Andrea Aime wrote:
Brent Owens ha scritto:
Hello developers and PSC members,
GSIP 5 has been up for a little while now and I think it is time to wrap it up and call a vote on it.
You can find it here: http://docs.codehaus.org/display/GEOS/GSIP+5+-+Release+processI will let people look over it for the next few days and maybe send out for a vote on tuesday.
Feel free to post more comments on the page or in email.
Here we go:
* release scheduling: sifficient -> sufficient
* release scheduling: once per month for the main development branches.
Hem, I agree from trunk, but what if a branch like 1.4.x did not
accumulate any interesting change?That's all, for the rest it's perfectly ok to me.
Cheers
Andrea
Brent Owens wrote:
Spelling:
- my speling sucksReleases once a month:
- I think GeoServer, overall, should have at least one release a month. If not more frequently. It shows that the project is very active and it also helps spreading the word of its existence.
But to handle perceptions of immaturity we need to be careful about these. Maybe we need a "critical upgrade recommendation" (big flashing icon) where folks are warned which releases matter if you have an installed base. Upgrading every month would be painful for a production system! Its bad enough for a developer who uses geoserver in the context of larger projects.
- Also, we usually manage a release every month or so anyways, even with not many fixes or changes
Brent Owens
(The Open Planning Project)Andrea Aime wrote:
Brent Owens ha scritto:
Hello developers and PSC members,
GSIP 5 has been up for a little while now and I think it is time to wrap it up and call a vote on it.
You can find it here: http://docs.codehaus.org/display/GEOS/GSIP+5+-+Release+processI will let people look over it for the next few days and maybe send out for a vote on tuesday.
Feel free to post more comments on the page or in email.
Here we go:
* release scheduling: sifficient -> sufficient
* release scheduling: once per month for the main development branches.
Hem, I agree from trunk, but what if a branch like 1.4.x did not
accumulate any interesting change?That's all, for the rest it's perfectly ok to me.
Cheers
Andrea-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
That's a good point Rob. Maybe we need better distinction between our minor and major releases. Or maybe the version number is sufficient? But a big flashing download button couldn't hurt.
What does everyone else think? For major releases (1.X) should we provide more notice that the release is major?
Brent Owens
(The Open Planning Project)
Rob Atkinson wrote:
Brent Owens wrote:
Spelling:
- my speling sucksReleases once a month:
- I think GeoServer, overall, should have at least one release a month. If not more frequently. It shows that the project is very active and it also helps spreading the word of its existence.
But to handle perceptions of immaturity we need to be careful about these. Maybe we need a "critical upgrade recommendation" (big flashing icon) where folks are warned which releases matter if you have an installed base. Upgrading every month would be painful for a production system! Its bad enough for a developer who uses geoserver in the context of larger projects.
- Also, we usually manage a release every month or so anyways, even with not many fixes or changes
Brent Owens
(The Open Planning Project)Andrea Aime wrote:
Brent Owens ha scritto:
Hello developers and PSC members,
GSIP 5 has been up for a little while now and I think it is time to wrap it up and call a vote on it.
You can find it here: http://docs.codehaus.org/display/GEOS/GSIP+5+-+Release+processI will let people look over it for the next few days and maybe send out for a vote on tuesday.
Feel free to post more comments on the page or in email.
Here we go:
* release scheduling: sifficient -> sufficient
* release scheduling: once per month for the main development branches.
Hem, I agree from trunk, but what if a branch like 1.4.x did not
accumulate any interesting change?That's all, for the rest it's perfectly ok to me.
Cheers
Andrea-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel