Hi, my 2 cents:
I am not sure why you want to focus on another 1.5.1 version soon. Its nice to have more releases but buggy releases aren't helpful either (though I understand that 1.5.1 is supposed to be more stable). Of course I don't know why we get good download rates, but having stable but fewer releases is from my perspective a positive thing - and this should be reached first by internal testing (and not user testing). So I agree here too that we shouldn't look too much at the OSGeo schedule for a next release - except we find some really heavy bugs in the 1.5.0 release. Hence, I support that next thing we do is * finish translations, * keep bug fixing, and * work on documentation. I am not in favour of new features, but they could be added with excluding them from the default-plugins for example? Ah.. and that idea of "branching": yes and no. The reason why GIT is used by many is because Merging in SVN isn't really working sooo well. I tried that at least 2 times and failed each time terribly (finally copying). But this depends of course on the type of changes done. I guess Benjamin has some experience here and could help. so -- seems more like 4 cents with respect to the length stefan Am 08.01.12 18:13, schrieb [email protected]: > On 08.01.2012 18:04, Michaël Michaud wrote: >> Hi, >>> don't worry about the plus release i'd say. let me add the maven profiles >>> for releases and generate CORE/PLUS together then. >> OK, >>> currently the files descriptor >>> http://sourceforge.net/projects/jump-pilot/files/OpenJUMP/osgeo/osgeo-5.5.files >>> points to 2597 snapshot which contains the latest fixes >> If I understand correctly, it will be easy to switch to any svn version >> we decide the d-day. >> Thanks for your effort, > > technically we can switch urls for oj,icon,data,doc, but yes we are free to > redirect > >>> if you insist, i usually do not like to have too many accounts everywhere, >>> i'll ask cameron >> Thanks, >> I learn slowly, and we'll really be more efficient this way ;o) >>> I finally think that it could be useful to have a 1.5.1 branch until >>> february >>> where one of us could commit safe updates from trunk (ex language files, >>> small fixes...) to be sure to have a rock solid version of OJ for the dvd >>> i leave that up to you. technically this won't be an obstacle, you only >>> have to take care to apply all fixes also to trunk everytime ;) send me the >>> branch details when you've set it up.. you can easily google howto branch >>> with subversive, don't be afraid, we can rollback everything. >> Just because I don't want to add new uncontrolled features in 1.5.1, >> but don't want to prevent other developpers to commit new features >> until february. >> >> As you are comitting many changes useful for installation/distribution, >> I'll wait some more days. > > i guess the release profiles will be done next week. for the time being we'll > probably negotiate a revision/branch and i start the build manually. as > already mentioned, in the future i could imagine a secured web interface for > such purposes. > >> If I create a branch (ideally after we've comitted distribution and >> language stuff and >> before we commit new features), we'll continue to use the trunk as usually >> and shouldn't have to use the 1.5.1 branch except to merge a useful >> bugfix... >> and to release 1.5.1. > > we are on one page regarding the feature freeze in the branch, let's see how > it'll work out :) .. ede > >> >> Michaël >> >>>> Sorry for the long mail >>>> Any comment is welcome. >>> done and done ... ede >>> >>>> >>>> >>>> >>>> Le 08/01/2012 13:42, Stefan Steiniger a écrit : >>>>> ok. >>>>> >>>>> I just tagged 1.4.2 (based on revision 2388) and 1.5. Though, for 1.5 I >>>>> took the last revision 2597 as I didn't know from where the version was >>>>> taken (but well.. if there is a problem we can just delete the tag and >>>>> create a new one). >>>>> >>>>> gonna have a look at OJs live-dvd documentation next. >>>>> stefan >>>>> >>>>> BTW: not sure if its links or copies.. but the process bar says >>>>> "copying" - maybe it makes "a copy of (revision) links" ;) >>>>> >>>>> Am 07.01.12 19:57, schrieb [email protected]: >>>>>> On 07.01.2012 19:19, Stefan Steiniger wrote: >>>>>>>>>> - ede, do you know how to setup the svn to create a >>>>>>>>>> a 1.5.0 tag and a 1.5.0 branch >>>>>>>>>> (trunk woul become the 1.6 branch ?) >>>>>>> I don't understand this - I did in the past a tag right after the >>>>>>> release (i.e. before any changes for the next version). I did this in >>>>>>> eclipse with subclipse - quite easy using a menu item. What happens then >>>>>>> is that simply the complete trunk folder is copied to that tag location. >>>>>>> >>>>>>> If you want I can see if I can do that again >>>>>>> stefan >>>>>>> >>>>>>> PS: or did I misunderstood you? >>>>>>> >>>>>> actually it's not copied but a virtual folder with links to the files at >>>>>> this revision is created. >>>>>> >>>>>> michael mentioned branching which would be equivalent but you could edit >>>>>> this branch and each edited file would get a new revision within this >>>>>> branch. >>>>>> >>>>>> michael simply forgot to tag in the past. that's all, nothing to worry >>>>>> here stefan.. ede >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex >>>>>> infrastructure or vast IT resources to deliver seamless, secure access to >>>>>> virtual desktops. With this all-in-one solution, easily deploy virtual >>>>>> desktops for less than the cost of PCs and save 60% on VDI infrastructure >>>>>> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox >>>>>> _______________________________________________ >>>>>> Jump-pilot-devel mailing list >>>>>> [email protected] >>>>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>>>> ------------------------------------------------------------------------------ >>>>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex >>>>> infrastructure or vast IT resources to deliver seamless, secure access to >>>>> virtual desktops. With this all-in-one solution, easily deploy virtual >>>>> desktops for less than the cost of PCs and save 60% on VDI infrastructure >>>>> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox >>>>> _______________________________________________ >>>>> Jump-pilot-devel mailing list >>>>> [email protected] >>>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>>>> >>>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex >>>> infrastructure or vast IT resources to deliver seamless, secure access to >>>> virtual desktops. With this all-in-one solution, easily deploy virtual >>>> desktops for less than the cost of PCs and save 60% on VDI infrastructure >>>> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox >>>> _______________________________________________ >>>> Jump-pilot-devel mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> ------------------------------------------------------------------------------ >>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex >>> infrastructure or vast IT resources to deliver seamless, secure access to >>> virtual desktops. With this all-in-one solution, easily deploy virtual >>> desktops for less than the cost of PCs and save 60% on VDI infrastructure >>> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> >>> >> >> >> ------------------------------------------------------------------------------ >> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex >> infrastructure or vast IT resources to deliver seamless, secure access to >> virtual desktops. With this all-in-one solution, easily deploy virtual >> desktops for less than the cost of PCs and save 60% on VDI infrastructure >> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox >> _______________________________________________ >> Jump-pilot-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > ------------------------------------------------------------------------------ > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > _______________________________________________ > Jump-pilot-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Jump-pilot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
