Ciao Jody,
I took the time to read the document, let me say that I will have to
read it again before I can comment it all in detail. Anyway the first
impression is very good.
About the community/unsupported/spike directory, I think we need to be
careful with the name we pick up though. To be honest, I would not
like to spend my nights workind on a coverage plugin listed as
unsopported!
I would suggest something like
+community
+development
+unsupported
+pending
+ext
Rationale.
If something goes out of the build for some reason we have
unsupported. If some new plugins are developed this work goes under
development until it meets the requirements for code coverage, etc....
When the requirements are met we move temporarly (1 month) to pending
and then to trunk. Ext is for extension to the library.
Anyway, apart from this, I would like to cause problems with the build
but I am like in stand-by because of this backport to 2.3.x. I could
port back everything within sunday (you know I can do pretty smooth
merges :-) ) but I want to be sure that everybody is happy with it
given the fact that people like adrian are struggling around the
release of 2.3.0.
If you guys prefere that I wait a bit for doing the back port I need
to know this not now but yesterday because I have some
presentations-demos to give soon and I can't stop the geoserver
development for more than a couple of days. It is worth to point out
that delaying the backport a bit not such a big deal, because we can
move geoserver raster to trunk for a little while and then suddenly
move it back to 2.3.x (even if I would rather not fo this). Alessio
ensured me that is no big deal.
Well, it is real late and I am tired, I hope I made my point and I
hope I did not cause too many troubles.
Ciao,
Simone.
On 10/4/06, Jody Garnett <[EMAIL PROTECTED]> wrote:
> Simone Giannecchini wrote:
> > Hi list,
> > in these last days I made a lot of people from the GeoTools, GeoServer
> > projects waste time in order to decide where to keep on doing
> > *stable* development for the current version of 2d raster support. My
> > definition of *stable* is, NO major API shift but only stable ordinary
> > bug fixes and new plugins for coverages.
> >
> > If I correctly understood all the ml that went around the answer is to
> > keep this *stable* development on geotools 2.3.x branch.
> >
> > So far so good. I have just a simple question now. Each time I
> > introduce a new plugin I put under spike for a while, asking people to
> > play with in order to remove as many bugs as possible before moving it
> > to the plugin dir. Well, the 2.3.x branch has no spike dir.
> >
> > Would it be worth to introduce a so-called community directory right
> > inside it which stays out of the build but which can be used to do
> > this kind of *stable* experiments?
> If you check out the "GTSteering" document you will see I make the same
> suggestion - but for different reasons. I am presenting the document to
> Paul today (although he has asked that I call such a directory
> "unsupported").
>
> Jody
>
--
-------------------------------------------------------
Eng. Simone Giannecchini
President /CEO GeoSolutions
http://www.geo-solutions.it
-------------------------------------------------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
