2009/7/25 gert <[email protected]>: > > On Jul 24, 12:53 pm, William Dode <[email protected]> wrote: >> On 24-07-2009, gert wrote: >> >> > On Jul 24, 9:54 am, William Dode <[email protected]> wrote: >> >> On 24-07-2009, Graham Dumpleton wrote: >> >> >> > This project isn't exactly one where many >> >> > people are working on it, so it is not like it brings any needed >> >> > features. >> >> >> I think there are a lot of people working on/with it that you don't see. >> >> mod_wsgi is a critical piece of software, it serve websites ! Just me, >> >> very little freelance, i serve 25 professional apps. For this i don't >> >> use the releases, but an hg branch from the svn that i follow carrefuly. >> >> One time for example i found a bug and you send me a patch that you >> >> didn't put immediatly on the svn. So after that, i had to take care that >> >> this patch was not erased by the svn... With an hg *private* branch >> >> i could more easily keep my patchs. And if somebody else wanted this >> >> patch that i tested, he could branch *my* branch. Then, when somes >> >> people had tested this patch on their private branch you could just pull >> >> one of them. >> >> >> Having said that, it's more important that you don't loose your time to >> >> switch if you're not ready for that. >> >> > Aldo Graham told me he had allot of work, i can safley conclude he >> > defenatly going to switch sooner or later now that he knows both svn >> > and hg can coexist in google. >> >> Are you sure they can coexist ? I believe we can switch from one to the >> other, but not use them together, i mean for the same branch. >> > > I think it is just two separated repo's one hg and one svn > The only thing that switches is the google interface. > > Anyway i can browse them both at the same time ? > http://appwsgi.googlecode.com/hg > http://appwsgi.googlecode.com/svn > > So he can already do his experiments in hg without touching svn > meaning the stuff you are interested in happens in hg and the boring > release stuff in svn
My interest in hg is only really to manage change on trunk head without actually making changes public. In that respect, I don't even need to use a public hg repository and could just use one on my own disk which is sucking from svn head. Ultimately I may want to start committing changes back for people to play with, but for that I probably don't want to touch subversion trunk as code may be drastically different and unstable and I know that some instructions out there promote check outs from trunk for live use, which is pretty stupid. As such, a public hg repository may be better. Even then, the development repository doesn't have to be hosted by Google Code and could equally be hosted by bitbucket and in some respects it would be safer to have it on bitbucket as much less risk then of stuff up more stable code base on Google Code. That all, said, it will not be something that I will be looking at until mod_wsgi 3.0 is released, I have caught up on some of the back log of documentation and I have time. There is also no point even doing it until I feel like starting on mod_wsgi 4.0, something which I have no idea when I may do as still not completely sure what I want to attempt to implement in that versions, despite my speculative roadmap I previously described. So, be patient. I will not happen next week. I still may never happen. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
