{"thread":{"id":"10180","subject":"Status of kha/experimental","startedAt":"2007-10-07T21:18:44Z","lastAt":"2007-10-12T08:56:28Z","messageCount":10,"participants":["Catalin Marinas","Karl Hasselström","Yann Dirson","David Kågedal"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"55087","messageId":"b0943d9e0710071418o6a664981i9d31db980c04bc50@mail.gmail.com","threadId":"10180","inReplyTo":null,"subject":"Status of kha/experimental","fromName":"Catalin Marinas","fromEmail":"catalin.marinas@gmail.com","sentAt":"2007-10-07T21:18:44Z","receivedAt":"2007-10-07T21:18:44Z","isPatch":false,"sender":{"key":"catalin.marinas@gmail.com","avatar":null},"body":"Hi Karl,\n\nHow stable is the kha/experimental branch? Since there are more and\nmore bugs added to the tracking system, I'll have to start looking at\nthem before a 0.14 release. Is it worth merging the kha/experimental\nnow or we better wait for after 0.14?\n\nThanks.\n\n-- \nCatalin\n"},{"id":"55090","messageId":"20071007213307.GA32210@diana.vm.bytemark.co.uk","threadId":"10180","inReplyTo":"b0943d9e0710071418o6a664981i9d31db980c04bc50@mail.gmail.com","subject":"Re: Status of kha/experimental","fromName":"Karl Hasselström","fromEmail":"kha@treskal.com","sentAt":"2007-10-07T21:33:07Z","receivedAt":"2007-10-07T21:33:07Z","isPatch":false,"sender":{"key":"kha@treskal.com","avatar":"https://gravatar.com/avatar/f0120c734b5279b345075a28521e1ac66acb20c9913ffe9bf6ae97e53f7f3f13?d=mp&s=160"},"body":"On 2007-10-07 22:18:44 +0100, Catalin Marinas wrote:\n\n> How stable is the kha/experimental branch? Since there are more and\n> more bugs added to the tracking system, I'll have to start looking\n> at them before a 0.14 release. Is it worth merging the\n> kha/experimental now or we better wait for after 0.14?\n\nThe idea is that experimental contains changes that need testing, but\nmay not yet be ready for your master. (They are generally safe,\nthough; I run StGit from my experimental branch at work, for example.)\nWhen I decide that they are ready, I move them to safe. If there are\nany patches you feel should be in safe rather than experimental, just\nask. Or you could just take them directly from experimental without\nasking, of course. :-)\n\n-- \nKarl Hasselström, kha@treskal.com\n www.treskal.com/kalle\n"},{"id":"55312","messageId":"b0943d9e0710091410w1559f1a0yb5055182fd289646@mail.gmail.com","threadId":"10180","inReplyTo":"20071007213307.GA32210@diana.vm.bytemark.co.uk","subject":"Re: Status of kha/experimental","fromName":"Catalin Marinas","fromEmail":"catalin.marinas@gmail.com","sentAt":"2007-10-09T21:10:12Z","receivedAt":"2007-10-09T21:10:12Z","isPatch":false,"sender":{"key":"catalin.marinas@gmail.com","avatar":null},"body":"On 07/10/2007, Karl Hasselström wrote:\n> On 2007-10-07 22:18:44 +0100, Catalin Marinas wrote:\n>\n> > How stable is the kha/experimental branch? Since there are more and\n> > more bugs added to the tracking system, I'll have to start looking\n> > at them before a 0.14 release. Is it worth merging the\n> > kha/experimental now or we better wait for after 0.14?\n>\n> The idea is that experimental contains changes that need testing, but\n> may not yet be ready for your master. (They are generally safe,\n> though; I run StGit from my experimental branch at work, for example.)\n> When I decide that they are ready, I move them to safe. If there are\n> any patches you feel should be in safe rather than experimental, just\n> ask. Or you could just take them directly from experimental without\n> asking, of course. :-)\n\nOK. My plan is to merge kha/safe and have a look at what seems safer\nto merge from kha/experimental. Fix bugs (and freeze the current\nfeatures). Release 0.14. Merge kha/experimental entirely post 0.14 and\ntest/stabilize it over couple of months. How does this sound?\n\n-- \nCatalin\n"},{"id":"55319","messageId":"20071009214613.GC26436@nan92-1-81-57-214-146.fbx.proxad.net","threadId":"10180","inReplyTo":"b0943d9e0710091410w1559f1a0yb5055182fd289646@mail.gmail.com","subject":"Re: Status of kha/experimental","fromName":"Yann Dirson","fromEmail":"ydirson@altern.org","sentAt":"2007-10-09T21:46:13Z","receivedAt":"2007-10-09T21:46:13Z","isPatch":false,"sender":{"key":"ydirson@altern.org","avatar":"https://avatars.githubusercontent.com/u/1190950?v=4"},"body":"On Tue, Oct 09, 2007 at 10:10:12PM +0100, Catalin Marinas wrote:\n> On 07/10/2007, Karl Hasselström wrote:\n> > On 2007-10-07 22:18:44 +0100, Catalin Marinas wrote:\n> >\n> > > How stable is the kha/experimental branch? Since there are more and\n> > > more bugs added to the tracking system, I'll have to start looking\n> > > at them before a 0.14 release. Is it worth merging the\n> > > kha/experimental now or we better wait for after 0.14?\n> >\n> > The idea is that experimental contains changes that need testing, but\n> > may not yet be ready for your master. (They are generally safe,\n> > though; I run StGit from my experimental branch at work, for example.)\n> > When I decide that they are ready, I move them to safe. If there are\n> > any patches you feel should be in safe rather than experimental, just\n> > ask. Or you could just take them directly from experimental without\n> > asking, of course. :-)\n> \n> OK. My plan is to merge kha/safe and have a look at what seems safer\n> to merge from kha/experimental. Fix bugs (and freeze the current\n> features). Release 0.14. Merge kha/experimental entirely post 0.14 and\n> test/stabilize it over couple of months. How does this sound?\n\nSounds like a good time to bring back my refactoring patches from the\nhydra patchset. I have not addressed yet the remarks that were voiced\nat that time, and the hydra patch itself has not been completed, and\nin fact the refactorings touch so many parts of the code that I can't\nenvision mantaining them outside the tree (in fact, I left them bitrot\nfor that very reason). If there is no other remarks than those\nalready posted as replies to the patchset, maybe we could consider\nmerging them soon after kha/experimental ?\n\nThat would require that I update them, but I'm not sure Karl would\nwant them in kha/experimental, since virtually any other patch causes\na conflict... The best situation would be that there would be a code\nfreeze at some time, during which I could update those patches without\ntoo much perturbations, but that may be asking a lot :)\n\nThe ideal situation would be if we would make diffcore and merge aware\nof a (de)indentation type of change. That's something I have felt the\nneed for since ages, but I'm unfortunately not going to find the time\nto implement that anytime soon :)\n\nBest regards,\n-- \nYann\n"},{"id":"55343","messageId":"87tzozxvto.fsf@lysator.liu.se","threadId":"10180","inReplyTo":"b0943d9e0710091410w1559f1a0yb5055182fd289646@mail.gmail.com","subject":"Re: Status of kha/experimental","fromName":"David Kågedal","fromEmail":"davidk@lysator.liu.se","sentAt":"2007-10-10T07:39:15Z","receivedAt":"2007-10-10T07:39:15Z","isPatch":false,"sender":{"key":"davidk@lysator.liu.se","avatar":"https://avatars.githubusercontent.com/u/60530?v=4"},"body":"\"Catalin Marinas\" writes:\n\n> On 07/10/2007, Karl Hasselström wrote:\n>> On 2007-10-07 22:18:44 +0100, Catalin Marinas wrote:\n>>\n>> > How stable is the kha/experimental branch? Since there are more and\n>> > more bugs added to the tracking system, I'll have to start looking\n>> > at them before a 0.14 release. Is it worth merging the\n>> > kha/experimental now or we better wait for after 0.14?\n>>\n>> The idea is that experimental contains changes that need testing, but\n>> may not yet be ready for your master. (They are generally safe,\n>> though; I run StGit from my experimental branch at work, for example.)\n>> When I decide that they are ready, I move them to safe. If there are\n>> any patches you feel should be in safe rather than experimental, just\n>> ask. Or you could just take them directly from experimental without\n>> asking, of course. :-)\n>\n> OK. My plan is to merge kha/safe and have a look at what seems safer\n> to merge from kha/experimental. Fix bugs (and freeze the current\n> features). Release 0.14. Merge kha/experimental entirely post 0.14 and\n> test/stabilize it over couple of months. How does this sound?\n\nSounds like a plan to me. But we should probably fix the loose ends\nin kha/experimental before merging it entirely.\n\n-- \nDavid Kågedal\n"},{"id":"55350","messageId":"20071010081718.GE12970@diana.vm.bytemark.co.uk","threadId":"10180","inReplyTo":"87tzozxvto.fsf@lysator.liu.se","subject":"Re: Status of kha/experimental","fromName":"Karl Hasselström","fromEmail":"kha@treskal.com","sentAt":"2007-10-10T08:17:18Z","receivedAt":"2007-10-10T08:17:18Z","isPatch":false,"sender":{"key":"kha@treskal.com","avatar":"https://gravatar.com/avatar/f0120c734b5279b345075a28521e1ac66acb20c9913ffe9bf6ae97e53f7f3f13?d=mp&s=160"},"body":"On 2007-10-10 09:39:15 +0200, David Kågedal wrote:\n\n> Sounds like a plan to me. But we should probably fix the loose ends\n> in kha/experimental before merging it entirely.\n\nI tried to list the loose ends in my last update. There weren't that\nmany of them as I recall.\n\n-- \nKarl Hasselström, kha@treskal.com\n www.treskal.com/kalle\n"},{"id":"55352","messageId":"20071010082602.GF12970@diana.vm.bytemark.co.uk","threadId":"10180","inReplyTo":"20071009214613.GC26436@nan92-1-81-57-214-146.fbx.proxad.net","subject":"Re: Status of kha/experimental","fromName":"Karl Hasselström","fromEmail":"kha@treskal.com","sentAt":"2007-10-10T08:26:02Z","receivedAt":"2007-10-10T08:26:02Z","isPatch":false,"sender":{"key":"kha@treskal.com","avatar":"https://gravatar.com/avatar/f0120c734b5279b345075a28521e1ac66acb20c9913ffe9bf6ae97e53f7f3f13?d=mp&s=160"},"body":"On 2007-10-09 23:46:13 +0200, Yann Dirson wrote:\n\n> That would require that I update them, but I'm not sure Karl would\n> want them in kha/experimental, since virtually any other patch\n> causes a conflict...\n\nRight. If it's likely to be many conflicts, I wouldn't mind if you\nwere the one who resolved them.\n\n> The best situation would be that there would be a code freeze at\n> some time, during which I could update those patches without too\n> much perturbations, but that may be asking a lot :)\n\nThere aren't that many of us working on StGit. If you can give a\nreasonably accurate start date and duration of the freeze, I don't\nthink it would be a problem. Others would simply have to be aware that\nany patches not merged before the freeze would have to be rebased on\ntop of your work once the freeze is over.\n\n-- \nKarl Hasselström, kha@treskal.com\n www.treskal.com/kalle\n"},{"id":"55500","messageId":"b0943d9e0710111338u109aa304o6ba9c886a42c2e24@mail.gmail.com","threadId":"10180","inReplyTo":"20071010082602.GF12970@diana.vm.bytemark.co.uk","subject":"Re: Status of kha/experimental","fromName":"Catalin Marinas","fromEmail":"catalin.marinas@gmail.com","sentAt":"2007-10-11T20:38:12Z","receivedAt":"2007-10-11T20:38:12Z","isPatch":false,"sender":{"key":"catalin.marinas@gmail.com","avatar":null},"body":"On 10/10/2007, Karl Hasselström wrote:\n> On 2007-10-09 23:46:13 +0200, Yann Dirson wrote:\n> > The best situation would be that there would be a code freeze at\n> > some time, during which I could update those patches without too\n> > much perturbations, but that may be asking a lot :)\n>\n> There aren't that many of us working on StGit. If you can give a\n> reasonably accurate start date and duration of the freeze,\n\nThis would mean that I have to be more organised :-).\n\n> I don't\n> think it would be a problem.Others would simply have to be aware that\n> any patches not merged before the freeze would have to be rebased on\n> top of your work once the freeze is over.\n\nI'll try - let's say we freeze it starting with the coming Monday\n(what's currently in kha/safe will be merged anyway) and aim to\nrelease 0.14 in about 3 weeks (or as soon as we fix the major bugs).\n\n-- \nCatalin\n"},{"id":"55531","messageId":"20071012074323.GB17403@diana.vm.bytemark.co.uk","threadId":"10180","inReplyTo":"b0943d9e0710111338u109aa304o6ba9c886a42c2e24@mail.gmail.com","subject":"Re: Status of kha/experimental","fromName":"Karl Hasselström","fromEmail":"kha@treskal.com","sentAt":"2007-10-12T07:43:23Z","receivedAt":"2007-10-12T07:43:23Z","isPatch":false,"sender":{"key":"kha@treskal.com","avatar":"https://gravatar.com/avatar/f0120c734b5279b345075a28521e1ac66acb20c9913ffe9bf6ae97e53f7f3f13?d=mp&s=160"},"body":"On 2007-10-11 21:38:12 +0100, Catalin Marinas wrote:\n\n> I'll try - let's say we freeze it starting with the coming Monday\n> (what's currently in kha/safe will be merged anyway) and aim to\n> release 0.14 in about 3 weeks (or as soon as we fix the major bugs).\n\nDo you have a list of the bugs you'd like to see fixed before the\nrelease? (I don't, I'm not organized. :-) )\n\n-- \nKarl Hasselström, kha@treskal.com\n www.treskal.com/kalle\n"},{"id":"55533","messageId":"b0943d9e0710120156x1ebea377od11e1175fabec4cf@mail.gmail.com","threadId":"10180","inReplyTo":"20071012074323.GB17403@diana.vm.bytemark.co.uk","subject":"Re: Status of kha/experimental","fromName":"Catalin Marinas","fromEmail":"catalin.marinas@gmail.com","sentAt":"2007-10-12T08:56:28Z","receivedAt":"2007-10-12T08:56:28Z","isPatch":false,"sender":{"key":"catalin.marinas@gmail.com","avatar":null},"body":"On 12/10/2007, Karl Hasselström wrote:\n> On 2007-10-11 21:38:12 +0100, Catalin Marinas wrote:\n>\n> > I'll try - let's say we freeze it starting with the coming Monday\n> > (what's currently in kha/safe will be merged anyway) and aim to\n> > release 0.14 in about 3 weeks (or as soon as we fix the major bugs).\n>\n> Do you have a list of the bugs you'd like to see fixed before the\n> release? (I don't, I'm not organized. :-) )\n\nhttps://gna.org/bugs/?group=stgit. All of them, if possible :-). If\nyou happen to work on any of them, change the \"assigned to\" filed so\nthat we don't duplicate the effort.\n\n-- \nCatalin\n"}]}