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 to grab the nightly build if they want my changes. It depends on how much lag time there is between my commit of a patch to the branch and the migration of the patch to the trunk. Let me know how you prefer to handle it. I'll do whatever you feel is easiest and best for the community. The Sunburned Surveyor On Thu, Apr 8, 2010 at 4:16 PM, Stefan Steiniger <[email protected]> wrote: > 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 wrote: >> 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 <[email protected]> wrote: >>> 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 check-out. >>> >>> hope you have more luck >>> stefan >>> >>> Sunburned Surveyor wrote: >>>> 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 first step >>>> would be modifying the code to report the FID of the problem feature >>>> in the exception message. At least, that is what I was going to try. >>>> You might have a short cut to the problem. >>>> >>>> You wrote: "There is another bug for which I spent some time without >>>> success : >>>> 2792806 Error while deleting heterogeneous item >>>> If you or someone else wants to have a look, it needs a good >>>> understanding of the item selection process (which is quite complex in >>>> OpenJUMP due to partial feature slection capability)" >>>> >>>> I've done a little work with the SelectionManager in my super select >>>> plug-in. I'll add this to my list of things to fix if I can. I'm just >>>> waiting for Stefan's permission to get a branch to work in. I'll copy >>>> him direction on this e-mail since I know he sometimes travels and >>>> looses track of the messages on this list. >>>> >>>> Thanks, >>>> >>>> The Sunburned Surveyor >>>> >>>> >>>> 2010/4/8 Michaël Michaud <[email protected]>: >>>>> 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 reproduce the problem. >>>>> >>>>> There is another bug for which I spent some time without success : >>>>> 2792806 Error while deleting heterogeneous item >>>>> If you or someone else wants to have a look, it needs a good >>>>> understanding of the item selection process (which is quite complex in >>>>> OpenJUMP due to partial feature slection capability) >>>>> >>>>> Michaël >>>>> >>>>> >>>>> >>>>> Sunburned Surveyor a écrit : >>>>>> 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 cut polygon >>>>>> tool obey the "editable" status of the layer that contains the polygon >>>>>> being cut; and (3) consolidation of some utility code. >>>>>> >>>>>> - Creation of a set of units tests to start testing the OpenJUMP core. >>>>>> I'll probably start with classes in the >>>>>> com.vividsolutions.jump.workbench.model packages, since those are the >>>>>> simplest. >>>>>> >>>>>> I would like to move these improvements to the trunk of the SVN, one >>>>>> at a time, after getting approval from the other programmers on this >>>>>> mailing list. I won't be proposing any major changes to the core, and >>>>>> will make sure I get buy off from everyone before commiting to the >>>>>> trunk. >>>>>> >>>>>> With Stefan's permission I'd like to start packaging monthly builds of >>>>>> this branch in between his major OpenJUMP releases. >>>>>> >>>>>> Any comments or strong objections? >>>>>> >>>>>> The Sunburned Surveyor >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Download Intel® Parallel Studio Eval >>>>>> Try the new software tools for yourself. Speed compiling, find bugs >>>>>> proactively, and fine-tune applications for parallel performance. >>>>>> See why Intel Parallel Studio got high marks during beta. >>>>>> http://p.sf.net/sfu/intel-sw-dev >>>>>> _______________________________________________ >>>>>> Jump-pilot-devel mailing list >>>>>> [email protected] >>>>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>>>>> >>>>>> >>>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Download Intel® Parallel Studio Eval >>>>> Try the new software tools for yourself. Speed compiling, find bugs >>>>> proactively, and fine-tune applications for parallel performance. >>>>> See why Intel Parallel Studio got high marks during beta. >>>>> http://p.sf.net/sfu/intel-sw-dev >>>>> _______________________________________________ >>>>> Jump-pilot-devel mailing list >>>>> [email protected] >>>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>>>> >>>> ------------------------------------------------------------------------------ >>>> Download Intel® Parallel Studio Eval >>>> Try the new software tools for yourself. Speed compiling, find bugs >>>> proactively, and fine-tune applications for parallel performance. >>>> See why Intel Parallel Studio got high marks during beta. >>>> http://p.sf.net/sfu/intel-sw-dev >>>> _______________________________________________ >>>> Jump-pilot-devel mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>>> >>>> >>> ------------------------------------------------------------------------------ >>> Download Intel® Parallel Studio Eval >>> Try the new software tools for yourself. Speed compiling, find bugs >>> proactively, and fine-tune applications for parallel performance. >>> See why Intel Parallel Studio got high marks during beta. >>> http://p.sf.net/sfu/intel-sw-dev >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Jump-pilot-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >> >> > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Jump-pilot-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Jump-pilot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
