I'd like to request permission to create a branch in the JPP SVN where
I can start work on two tasks:
- A series of bug fixes and minor improvements. These fixes include
(1) reporting the FID in the Union By Attribute plug-in to address a
problem reported some time ago by Nacho; (2) making the
Hi Sunburned Surveyor
Fixing these bugs would be nice and starting unit tests would be nice too.
I forgot bug (1) reported by Nacho as it has never been reported in the
bug tracker.
I can have a look this week end as I think I wrote the guilty plugin,
and Nacho kindly supplied the data to
Michael,
You wrote: I forgot bug (1) reported by Nacho as it has never been
reported in the
bug tracker. I can have a look this week end as I think I wrote the
guilty plugin,
and Nacho kindly supplied the data to reproduce the problem.
Thanks for offering to help with Nacho's bug. I think the
Hi SS,
I think bug fixing should be done in the trunk so that you get feedback as
soon as possible.
Can you be more specific about utility code consolidation? Branching the
code isn't really going to help us evaluate your changes. If they aren't
too controversial, I'd rather they be done
Hei Landon,
Yep - no problem to create a new branch. You should be able to do that.
However, I tried branching once lately, and messed-up my local system,
i.e. I wasn't able to re-integrate (merge) my changes to the branch back
without copy pasting to another folder and then do a complete new
Larry,
Thanks for the response.
You wrote: I think bug fixing should be done in the trunk so that you
get feedback as soon as possible.
I only thought of branching for two (2) reasons:
(1) So I don't break the nightly build with my changes.
(2) So I can produce a regular build of the branch
Thanks for your permission Stefan. I'll wait for Larry to respond. If
he gives me the OK after reading my response to his questions I will
create the branch.
The Sunburned Surveyor
On Thu, Apr 8, 2010 at 2:38 PM, Stefan Steiniger sst...@geo.uzh.ch wrote:
Hei Landon,
Yep - no problem to create
btw.
some thing I did not really understand: why do you want to do monthly
releases? because we have already a nightly build which get done
automatically as soon changes appear (if i remember correctly) - though
- it may be that these changes have to be in the trunk.
stefan
Sunburned Surveyor
I think our nightly build is based on the trunk. That means I'll need
a regular build of the branch. My goal for monthly releases of the
branch was to get my changes out for testing to the OpenJUMP community
without breaking the nightly build.
I'm not picky about this. I can just tell the users
