So Justin do we have a release week going down? What needs doing ...
(I will not even ask what you are doing after reading those catalog questions)
Jody
Thanks Jody, you beat me to the punch. Basically its all about docs for the next milestone. Jody and were actually able to agree on a table of contents.
Here is the current TOC:
1. Overview
2. Setup
3. Development
0. Source Code
1. Compiling
...
4. Programmers Guide
0 Definitions
1 Spring
2 A Simple Plugin
3 Bundling your Plugin
4 Extension
As the target TOC:
1. Overview
2. Setup
3. Maven Quickstart
4. Eclipse Quickstart
5. Programmers Guide
1. GeoServer Architecture
2. GeoServer Platform
3. Simple PlugIn
4. Modules
1. Data
6. Reference
1. Javadocs
2. Extension Poins
Here is what needs to be done :
1. Overview -> Done
2. Setup -> Done
3. Maven Quickstart -> Needs to be ripped out of the current "Development" section. Basically taking the following sections and merging them into a single page:
0 Source Code
1 Compiling
2 Deploying
4 Running
4. Eclipse Quickstart -> Needs to be ripped out of the current "Development" section. Basically taking the following sections and merging them into a single page:
6 Building with Eclipse
5 Debugging
5.1 GeoServer Aritecture -> *Short* architecture overview with a picture. Can take the picture either from the VWFS docs, or from the 1 Spring page of the current docs.
5.2 GeoServer Platform -> How we use spring. Mostly just the 1 Spring page made nicer ( talk to Jody for feedback ). We might also want to steal the picture from 4 Extension of the current docs.
5.3 Simple PlugIn -> Done, take from current docs
5.4 Bundling your PlugIn -> Done? I think. This really doesn't work very well with the current module setup because you have to drag all the config stuff along. It might be worth killing this for now until after release.
5.4 Modules -> Work in progress, I would like this to be modules documented as they pass certain Q/A checks, code reviews, have decent javadocs. As for now we can document the "data" module.
6.2 Extension Points -> Work in progress. Similar to the module system we can document as we go and Q/A. This is just a reference section with a list of the extension points, started on page 4 Extension of the current docs.
So we have a busy week, I beleive you are able to throw some resources on some of this jody?
-Justin
Jody Garnett wrote:
So Justin do we have a release week going down? What needs doing ...
(I will not even ask what you are doing after reading those catalog questions)
JodyUsing 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!DSPAM:1004,44a8e41662512081064789!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Cool.
Thanks Jody, you beat me to the punch. Basically its all about docs for the next milestone.
Sweet now if only I could keep up w/ those catalog questions...
So how do you want to run this oh team lead type ... got Jira? Got the todo list on the web page ... or are you hoping email will cut it?
Jody and were actually able to agree on a table of contents.
Of course the fun part is capturing the "why..." how about I take the writing guidelines section 
5.1 GeoServer Aritecture -> *Short* architecture overview with a picture. Can take the picture either from the VWFS docs, or from the 1 Spring page of the current docs.
5.2 GeoServer Platform -> How we use spring. Mostly just the 1 Spring page made nicer ( talk to Jody for feedback ). We might also want to steal the picture from 4 Extension of the current docs.
5.3 Simple PlugIn -> Done, take from current docs
5.4 Bundling your PlugIn -> Done? I think. This really doesn't work very well with the current module setup because you have to drag all the config stuff along. It might be worth killing this for now until after release.
Could we make an easier plugin? I figure this is important for the message of GeoServer 1.4.x - "aka you can now hack". Do not suppose we can grab the annoying conf stuff as a maven dependency? Conf is really annoying me... kind of wish people could download conf as a data directory, and have the web application ask you where your data directory is the first time you run it...
5.4 Modules -> Work in progress, I would like this to be modules documented as they pass certain Q/A checks, code reviews, have decent javadocs. As for now we can document the "data" module.
Having the first one documented will be a good example, and nothing is harder then the data module.
6.2 Extension Points -> Work in progress. Similar to the module system we can document as we go and Q/A. This is just a reference section with a list of the extension points, started on page 4 Extension of the current docs.
So we have a busy week, I beleive you are able to throw some resources on some of this jody?
I have some time set aside ... how do you want to organize?
- help with release/test/upload?
- diagrams
- content
- review/edit
- shuffling pages around?
You also missed a section, we are going to be done "prepping" these pages soon. We should plan to move them into GEOSDOC on say thursday? Also need a migration plan on how to move these pages and what to do with existing "devel" content...
1. move pages keeping parent/child relationships
2. move existing devel articles to 6.3. Other Reference Material
Cheers,
Jody
Jody Garnett wrote:
Cool.
Thanks Jody, you beat me to the punch. Basically its all about docs for the next milestone.
Sweet now if only I could keep up w/ those catalog questions...
So how do you want to run this oh team lead type ... got Jira? Got the todo list on the web page ... or are you hoping email will cut it?
I would like to use jira yes. We can throw the major documentation tasks into jira. We can also use teh documentation todo tasks for stuff that needs to be done later. Basically i dont want to get hung up on nit picky details.
Jody and were actually able to agree on a table of contents.
Of course the fun part is capturing the "why..." how about I take the writing guidelines section
Sounds good to me.
5.1 GeoServer Aritecture -> *Short* architecture overview with a picture. Can take the picture either from the VWFS docs, or from the 1 Spring page of the current docs.
5.2 GeoServer Platform -> How we use spring. Mostly just the 1 Spring page made nicer ( talk to Jody for feedback ). We might also want to steal the picture from 4 Extension of the current docs.
5.3 Simple PlugIn -> Done, take from current docs
5.4 Bundling your PlugIn -> Done? I think. This really doesn't work very well with the current module setup because you have to drag all the config stuff along. It might be worth killing this for now until after release.Could we make an easier plugin? I figure this is important for the message of GeoServer 1.4.x - "aka you can now hack". Do not suppose we can grab the annoying conf stuff as a maven dependency? Conf is really annoying me... kind of wish people could download conf as a data directory, and have the web application ask you where your data directory is the first time you run it...
Well the problem is the dispatching framework is tied to the config. Untiing them is a lot of work. We could use the http dispatcher community module, however it needs a code review and some more testing. Also the hello world plugin would have to be changed slightly since the thing isn't really servlet based anymore, that would be simple enough though. This might not be a bad idea. WFS 1.1 will be using the new dispatcher so at some point this will have to be done.
So how about this. We TODO this one for now and make it lesser priority for the moment and get to it later on in the week. Like I said I dont want to get hung up.
5.4 Modules -> Work in progress, I would like this to be modules documented as they pass certain Q/A checks, code reviews, have decent javadocs. As for now we can document the "data" module.
Having the first one documented will be a good example, and nothing is harder then the data module.
I can do this.
6.2 Extension Points -> Work in progress. Similar to the module system we can document as we go and Q/A. This is just a reference section with a list of the extension points, started on page 4 Extension of the current docs.
So we have a busy week, I beleive you are able to throw some resources on some of this jody?
I have some time set aside ... how do you want to organize?
- help with release/test/upload?
- diagrams
- content
- review/edit
- shuffling pages around?
I think if you could put some people on shuffling pages around that would be great. Cite tests would also be nice but i know its not really an option for you folks in SA. Perhaps one the remote team members?
You also missed a section, we are going to be done "prepping" these pages soon. We should plan to move them into GEOSDOC on say thursday? Also need a migration plan on how to move these pages and what to do with existing "devel" content...
Right. I think we need to talk to chris and brent about wether they want this done before or after 1.4.x gets to trunk. But this should be easy enough.
1. Swap out old developers guide with new one.
2. Throw content from old developers guide that is worth saving into refrence section of the new one, or somewhere else if it makes sense.
1. move pages keeping parent/child relationships
2. move existing devel articles to 6.3. Other Reference MaterialCheers,
Jody!DSPAM:1004,44a8f6e567671429667743!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Justin Deoliveira wrote:
I would like to use jira yes. We can throw the major documentation tasks into jira. We can also use teh documentation todo tasks for stuff that needs to be done later. Basically i dont want to get hung up on nit picky details.
I will make sure we are set up with Jira here...
Jody and were actually able to agree on a table of contents.
Of course the fun part is capturing the "why..." how about I take the writing guidelines section
Sounds good to me.
Well the problem is the dispatching framework is tied to the config. Untiing them is a lot of work. We could use the http dispatcher community module, however it needs a code review and some more testing. Also the hello world plugin would have to be changed slightly since the thing isn't really servlet based anymore, that would be simple enough though. This might not be a bad idea. WFS 1.1 will be using the new dispatcher so at some point this will have to be done.
Sigh ... new dispatcher ... will wait till I read the docs.
So how about this. We TODO this one for now and make it lesser priority for the moment and get to it later on in the week. Like I said I dont want to get hung up.
Well we need something before 1.4.0 ... that said Jesse is already making useful community plug-ins...
I think if you could put some people on shuffling pages around that would be great. Cite tests would also be nice but i know its not really an option for you folks in SA. Perhaps one the remote team members?
Well put these all down as tasks in Jira, and put some times next to them...
You also missed a section, we are going to be done "prepping" these pages soon. We should plan to move them into GEOSDOC on say thursday? Also need a migration plan on how to move these pages and what to do with existing "devel" content...
Right. I think we need to talk to chris and brent about wether they want this done before or after 1.4.x gets to trunk. But this should be easy enough.
1. Swap out old developers guide with new one.
2. Throw content from old developers guide that is worth saving into refrence section of the new one, or somewhere else if it makes sense.
Well we were asked for the complete plan, and explicitly what to do with those pages ... so lets move it into section 6.3 and call it a day. As long as there is no PSC lets just talk about this on the geoserver IRC meeting and then get to work updating GEOSDOC Wednesday? If they plan any more 1.3.x release they may want to grab an export or something ...
Jody
Jody Garnett wrote:
Justin Deoliveira wrote:
I would like to use jira yes. We can throw the major documentation tasks into jira. We can also use teh documentation todo tasks for stuff that needs to be done later. Basically i dont want to get hung up on nit picky details.
I will make sure we are set up with Jira here...
Cool, for now i am leaving them unassigned. We can assign to your guys once they have accounts.
Jody and were actually able to agree on a table of contents.
Of course the fun part is capturing the "why..." how about I take the writing guidelines section
Sounds good to me.
Well the problem is the dispatching framework is tied to the config. Untiing them is a lot of work. We could use the http dispatcher community module, however it needs a code review and some more testing. Also the hello world plugin would have to be changed slightly since the thing isn't really servlet based anymore, that would be simple enough though. This might not be a bad idea. WFS 1.1 will be using the new dispatcher so at some point this will have to be done.Sigh ... new dispatcher ... will wait till I read the docs.
The reason it is still community is because I havent had time to doc. But you shouldn't have to read too much, you did help me design it 
So how about this. We TODO this one for now and make it lesser priority for the moment and get to it later on in the week. Like I said I dont want to get hung up.
Well we need something before 1.4.0 ... that said Jesse is already making useful community plug-ins...
Fair enough. Definitley before 1.4.0, but perhaps not for 1.4.0-M0. I will create the jira task regardless, we may want to reschedule for a bit later.
I think if you could put some people on shuffling pages around that would be great. Cite tests would also be nice but i know its not really an option for you folks in SA. Perhaps one the remote team members?
Well put these all down as tasks in Jira, and put some times next to them...
You also missed a section, we are going to be done "prepping" these pages soon. We should plan to move them into GEOSDOC on say thursday? Also need a migration plan on how to move these pages and what to do with existing "devel" content...
Right. I think we need to talk to chris and brent about wether they want this done before or after 1.4.x gets to trunk. But this should be easy enough.
1. Swap out old developers guide with new one.
2. Throw content from old developers guide that is worth saving into refrence section of the new one, or somewhere else if it makes sense.Well we were asked for the complete plan, and explicitly what to do with those pages ... so lets move it into section 6.3 and call it a day. As long as there is no PSC lets just talk about this on the geoserver IRC meeting and then get to work updating GEOSDOC Wednesday? If they plan any more 1.3.x release they may want to grab an export or something ...
Sounds good. We also need to do another sync up with trunk before 1.4.0. It is probably a good idea to do for M1. Basically it would be nice to have M1 be the last release which has code changes. Not sure if that is going to be possible givin your deadline perhaps.
Jody
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!DSPAM:1004,44a8fd1469894750375898!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Justin Deoliveira wrote:
I will make sure we are set up with Jira here...
Cool, for now i am leaving them unassigned. We can assign to your guys once they have accounts.
Oh I suppose I have one somewhere...
- jgarnett
Can we get the roadmap to reflect reality ... you are a Jira admin are you not?
- http://jira.codehaus.org/secure/BrowseProject.jspa?id=10311&subset=-1
I noticed you are targeting 1.4.0-M1 ... ?
Well we were asked for the complete plan, and explicitly what to do with those pages ... so lets move it into section 6.3 and call it a day. As long as there is no PSC lets just talk about this on the geoserver IRC meeting and then get to work updating GEOSDOC Wednesday? If they plan any more 1.3.x release they may want to grab an export or something ...
Sounds good. We also need to do another sync up with trunk before 1.4.0. It is probably a good idea to do for M1. Basically it would be nice to have M1 be the last release which has code changes. Not sure if that is going to be possible givin your deadline perhaps.
Or perhaps your planning Should we make a M1 for Wednesday then ... I could relax the deadline by a week (until the 14th), but would more time actually buy you anything?
Jody
Jira all setup.
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10311&fixfor=12710
A few of the tasks are assigned to myself, one to Jody. Jody do you think you can march through and assign some of the unassigned to your team. Thanks.
Jody Garnett wrote:
Justin Deoliveira wrote:
I will make sure we are set up with Jira here...
Cool, for now i am leaving them unassigned. We can assign to your guys once they have accounts.
Oh I suppose I have one somewhere...
- jgarnettCan we get the roadmap to reflect reality ... you are a Jira admin are you not?
- http://jira.codehaus.org/secure/BrowseProject.jspa?id=10311&subset=-1I noticed you are targeting 1.4.0-M1 ... ?
Well we were asked for the complete plan, and explicitly what to do with those pages ... so lets move it into section 6.3 and call it a day. As long as there is no PSC lets just talk about this on the geoserver IRC meeting and then get to work updating GEOSDOC Wednesday? If they plan any more 1.3.x release they may want to grab an export or something ...
Sounds good. We also need to do another sync up with trunk before 1.4.0. It is probably a good idea to do for M1. Basically it would be nice to have M1 be the last release which has code changes. Not sure if that is going to be possible givin your deadline perhaps.
Or perhaps your planning
I was thinking more of M1 for end of work, and RC0 end of next week. There are a few other factors to consider as well such as wcs branch and current trunk work. I am going to send an email and set up our next IRC.
Jody
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!DSPAM:1004,44a902b474374750375898!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Cool.
So a prerequisite to getting 1.4.x onto trunk is that everyone will have to get "out of the pool" on trunk.
Brent, Chris: After 1.3.2 what are further developent plans. Basically does it work for you guys to do the 1.4.x merge then?
-Justin
Brent Owens wrote:
We are releasing a 1.3.2 version this week. It should be a very solid
release and worth syncing up with.-Brent
On 7/3/06, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Jira all setup.
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10311&fixfor=12710
A few of the tasks are assigned to myself, one to Jody. Jody do you
think you can march through and assign some of the unassigned to your
team. Thanks.Jody Garnett wrote:
> Justin Deoliveira wrote:
>
>>>I will make sure we are set up with Jira here...
>>
>>Cool, for now i am leaving them unassigned. We can assign to your guys
>>once they have accounts.
>
> Oh I suppose I have one somewhere...
> - jgarnett
>
> Can we get the roadmap to reflect reality ... you are a Jira admin are
> you not?
> - http://jira.codehaus.org/secure/BrowseProject.jspa?id=10311&subset=-1
>
> I noticed you are targeting 1.4.0-M1 ... ?
>
>>>Well we were asked for the complete plan, and explicitly what to do
>>>with those pages ... so lets move it into section 6.3 and call it a
>>>day. As long as there is no PSC lets just talk about this on the
>>>geoserver IRC meeting and then get to work updating GEOSDOC
>>>Wednesday? If they plan any more 1.3.x release they may want to grab
>>>an export or something ...
>>
>>Sounds good. We also need to do another sync up with trunk before
>>1.4.0. It is probably a good idea to do for M1. Basically it would be
>>nice to have M1 be the last release which has code changes. Not sure
>>if that is going to be possible givin your deadline perhaps.
>
> Or perhaps your planning
> I could relax the deadline by a week (until the 14th), but would more
> time actually buy you anything?
I was thinking more of M1 for end of work, and RC0 end of next week.
There are a few other factors to consider as well such as wcs branch and
current trunk work. I am going to send an email and set up our next IRC.
>
> Jody
>
> 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
>
> >--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.comUsing 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!DSPAM:1004,44a940a698636309890654!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Justin Deoliveira wrote:
Cool.
So a prerequisite to getting 1.4.x onto trunk is that everyone will have to get "out of the pool" on trunk.
Brent, Chris: After 1.3.2 what are further developent plans. Basically does it work for you guys to do the 1.4.x merge then?
That should work. We're planning a release on wednesday. So after that we should make a 1.3.x branch. Then trunk will be open for you to do the switcheroo. Once you guys get to RC1, with all the KML stuff on right, we'll switch development focus there from the 1.3.x branch. There's some stuff in the works, but if 1.4.x is in RC's then we can just develop there. Note that I'd only like 1-2 RC releases ideally, none of that RC8 of 1.3.x. RC should mean a freeze on everything except fixes.
C
-Justin
Brent Owens wrote:
We are releasing a 1.3.2 version this week. It should be a very solid
release and worth syncing up with.-Brent
On 7/3/06, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Jira all setup.
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10311&fixfor=12710
A few of the tasks are assigned to myself, one to Jody. Jody do you
think you can march through and assign some of the unassigned to your
team. Thanks.Jody Garnett wrote:
> Justin Deoliveira wrote:
>
>>>I will make sure we are set up with Jira here...
>>
>>Cool, for now i am leaving them unassigned. We can assign to your guys
>>once they have accounts.
>
> Oh I suppose I have one somewhere...
> - jgarnett
>
> Can we get the roadmap to reflect reality ... you are a Jira admin are
> you not?
> - http://jira.codehaus.org/secure/BrowseProject.jspa?id=10311&subset=-1
>
> I noticed you are targeting 1.4.0-M1 ... ?
>
>>>Well we were asked for the complete plan, and explicitly what to do
>>>with those pages ... so lets move it into section 6.3 and call it a
>>>day. As long as there is no PSC lets just talk about this on the
>>>geoserver IRC meeting and then get to work updating GEOSDOC
>>>Wednesday? If they plan any more 1.3.x release they may want to grab
>>>an export or something ...
>>
>>Sounds good. We also need to do another sync up with trunk before
>>1.4.0. It is probably a good idea to do for M1. Basically it would be
>>nice to have M1 be the last release which has code changes. Not sure
>>if that is going to be possible givin your deadline perhaps.
>
> Or perhaps your planning
> I could relax the deadline by a week (until the 14th), but would more
> time actually buy you anything?
I was thinking more of M1 for end of work, and RC0 end of next week.
There are a few other factors to consider as well such as wcs branch and
current trunk work. I am going to send an email and set up our next IRC.
>
> Jody
>
> 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
>
> >--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.comUsing 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
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
Chris Holmes wrote:
Justin Deoliveira wrote:
Cool.
So a prerequisite to getting 1.4.x onto trunk is that everyone will have to get "out of the pool" on trunk.
Brent, Chris: After 1.3.2 what are further developent plans. Basically does it work for you guys to do the 1.4.x merge then?
That should work. We're planning a release on wednesday. So after that we should make a 1.3.x branch. Then trunk will be open for you to do the switcheroo. Once you guys get to RC1, with all the KML stuff on right, we'll switch development focus there from the 1.3.x branch.
I am doing a sync up right now, I will do another one after 1.3.2 is tagged. As soon as 1.3.2 gets tagged we can branch 1.3.x and then switch. Should be pretty seemless. The only pain will be you will have to check out trunk again from scratch.
There's some stuff in the works, but if 1.4.x is in RC's then we can just develop there. Note that I'd only like 1-2 RC releases ideally, none of that RC8 of 1.3.x. RC should mean a freeze on everything except fixes.
Absolutley. Once we get to RC0 I would like to see a code freeze minus merging any more changes from trunk.
C
-Justin
Brent Owens wrote:
We are releasing a 1.3.2 version this week. It should be a very solid
release and worth syncing up with.-Brent
On 7/3/06, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Jira all setup.
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10311&fixfor=12710
A few of the tasks are assigned to myself, one to Jody. Jody do you
think you can march through and assign some of the unassigned to your
team. Thanks.Jody Garnett wrote:
> Justin Deoliveira wrote:
>
>>>I will make sure we are set up with Jira here...
>>
>>Cool, for now i am leaving them unassigned. We can assign to your guys
>>once they have accounts.
>
> Oh I suppose I have one somewhere...
> - jgarnett
>
> Can we get the roadmap to reflect reality ... you are a Jira admin are
> you not?
> - http://jira.codehaus.org/secure/BrowseProject.jspa?id=10311&subset=-1
>
> I noticed you are targeting 1.4.0-M1 ... ?
>
>>>Well we were asked for the complete plan, and explicitly what to do
>>>with those pages ... so lets move it into section 6.3 and call it a
>>>day. As long as there is no PSC lets just talk about this on the
>>>geoserver IRC meeting and then get to work updating GEOSDOC
>>>Wednesday? If they plan any more 1.3.x release they may want to grab
>>>an export or something ...
>>
>>Sounds good. We also need to do another sync up with trunk before
>>1.4.0. It is probably a good idea to do for M1. Basically it would be
>>nice to have M1 be the last release which has code changes. Not sure
>>if that is going to be possible givin your deadline perhaps.
>
> Or perhaps your planning
> I could relax the deadline by a week (until the 14th), but would more
> time actually buy you anything?
I was thinking more of M1 for end of work, and RC0 end of next week.
There are a few other factors to consider as well such as wcs branch and
current trunk work. I am going to send an email and set up our next IRC.
>
> Jody
>
> 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
>
> >--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.comUsing 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
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Hey Brent,
Can you send this kind of information to the devel list, we would like to work with you. Checking Jira roadmap I see that you do have
1.3.2 scheduled for June 27th.
Do you have a plan for integration w/ 1.4.x? I suppose I just want to know what dates things are going down on ... what is the point of 1.3.2 etc... stuff we can cover in the meeting tomorrow. I trust you want to take a copy of GEOSDOC before we start intergrating 1.4.x content? Can you do an export on Tuesday please.
Jody
We are releasing a 1.3.2 version this week. It should be a very solid
release and worth syncing up with.-Brent
On 7/3/06, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Jira all setup.
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10311&fixfor=12710
A few of the tasks are assigned to myself, one to Jody. Jody do you
think you can march through and assign some of the unassigned to your
team. Thanks.Jody Garnett wrote:
> Justin Deoliveira wrote:
>
>>>I will make sure we are set up with Jira here...
>>
>>Cool, for now i am leaving them unassigned. We can assign to your guys
>>once they have accounts.
>
> Oh I suppose I have one somewhere...
> - jgarnett
>
> Can we get the roadmap to reflect reality ... you are a Jira admin are
> you not?
> - http://jira.codehaus.org/secure/BrowseProject.jspa?id=10311&subset=-1
>
> I noticed you are targeting 1.4.0-M1 ... ?
>
>>>Well we were asked for the complete plan, and explicitly what to do
>>>with those pages ... so lets move it into section 6.3 and call it a
>>>day. As long as there is no PSC lets just talk about this on the
>>>geoserver IRC meeting and then get to work updating GEOSDOC
>>>Wednesday? If they plan any more 1.3.x release they may want to grab
>>>an export or something ...
>>
>>Sounds good. We also need to do another sync up with trunk before
>>1.4.0. It is probably a good idea to do for M1. Basically it would be
>>nice to have M1 be the last release which has code changes. Not sure
>>if that is going to be possible givin your deadline perhaps.
>
> Or perhaps your planning
> I could relax the deadline by a week (until the 14th), but would more
> time actually buy you anything?
I was thinking more of M1 for end of work, and RC0 end of next week.
There are a few other factors to consider as well such as wcs branch and
current trunk work. I am going to send an email and set up our next IRC.
>
> Jody
>
> 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
>
> !DSPAM:1004,44a902b474374750375898!
>--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.comUsing 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
Hi Jody,
It looks like after 1.3.2, people developing on trunk are willing to get out of the pool and let us go forward with the 1.4.x switch.
-Justin
Jody Garnett wrote:
Hey Brent,
Can you send this kind of information to the devel list, we would like to work with you. Checking Jira roadmap I see that you do have
1.3.2 scheduled for June 27th.Do you have a plan for integration w/ 1.4.x? I suppose I just want to know what dates things are going down on ... what is the point of 1.3.2 etc... stuff we can cover in the meeting tomorrow. I trust you want to take a copy of GEOSDOC before we start intergrating 1.4.x content? Can you do an export on Tuesday please.
Jody
We are releasing a 1.3.2 version this week. It should be a very solid
release and worth syncing up with.-Brent
On 7/3/06, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Jira all setup.
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10311&fixfor=12710
A few of the tasks are assigned to myself, one to Jody. Jody do you
think you can march through and assign some of the unassigned to your
team. Thanks.Jody Garnett wrote:
Justin Deoliveira wrote:
I will make sure we are set up with Jira here...
Cool, for now i am leaving them unassigned. We can assign to your guys
once they have accounts.Oh I suppose I have one somewhere...
- jgarnettCan we get the roadmap to reflect reality ... you are a Jira admin are
you not?
-http://jira.codehaus.org/secure/BrowseProject.jspa?id=10311&subset=-1
I noticed you are targeting 1.4.0-M1 ... ?
Well we were asked for the complete plan, and explicitly what to do
with those pages ... so lets move it into section 6.3 and call it a
day. As long as there is no PSC lets just talk about this on the
geoserver IRC meeting and then get to work updating GEOSDOC
Wednesday? If they plan any more 1.3.x release they may want to grab
an export or something ...Sounds good. We also need to do another sync up with trunk before
1.4.0. It is probably a good idea to do for M1. Basically it would be
nice to have M1 be the last release which has code changes. Not sure
if that is going to be possible givin your deadline perhaps.Or perhaps your planning
then ...
I could relax the deadline by a week (until the 14th), but would more
time actually buy you anything?I was thinking more of M1 for end of work, and RC0 end of next week.
There are a few other factors to consider as well such as wcs branch and
current trunk work. I am going to send an email and set up our next IRC.Jody
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--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.comUsing 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-develUsing 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!DSPAM:1004,44a96446133638365517736!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Justin Deoliveira wrote:
Hi Jody,
It looks like after 1.3.2, people developing on trunk are willing to get out of the pool and let us go forward with the 1.4.x switch.
Sweet. Do we need to hold off on doc merge until 1.3.2 takes a copy of GEOSDOC?
Jody