On 07/11/06, Gábor Farkas <[EMAIL PROTECTED]> wrote: > > Jay Parlar wrote: > > On 11/6/06, David Blewett <[EMAIL PROTECTED]> wrote: > >> I would like to suggest that the branches that are felt to be complete > >> sans testing be merged into a single branch. I am anxiously awaiting > >> several different branch merges to core but do not have time to check > >> each individual one out to test them. Maybe it's time to begin a larger > >> effort, similar to magic-removal, at merging all these branches? > > > > This is a constant complaint we're seeing now. The problem is, not > > enough people are actually jumping in and testing out the branches. > > The core devs tell people all the time that it's generally safe to run > > Django off the trunk, but if a bunch of untested branches are merged > > in, well, welcome to disaster time. > > > (what follows will be a little critical. please don't get it wrong. i > simply am stating what i think is wrong, and what should be done so that > we can move on, and finish/merge these branches) > > i think the problem is also the documentation (well, the lack of it). > > for example, i was trying to do some branch-testing (actually what i > want is the birth of the unicode-branch, but currently the best way to > achieve it seems to merge the other branches into the trunk :), > > so i arrived at: > > http://code.djangoproject.com/wiki/ActiveBranches > > the status of the various branches: > > for the following 4 branches, the activeBranches page says that they > need end-user testing: > ================================ > - fullHistory > - http://code.djangoproject.com/wiki/FullHistory says "Status: Almost > there", and below it's shown that some parts are not done yet > > - rowLevelPermissions > - the http://code.djangoproject.com/wiki/RowLevelPermissionsDeveloper > shows some unit-tests that still do not pass > > - schemaEvolution > - the wiki-pages only talk about (at least 2 different) proposals. > does > that mean that one of the proposals has been implemented? which one? >
I don't think any of those proposals reflect what is actually implemented. I've used the schema-evolution branch and have had some issues which are yet to be resolved or even responded to by the developer. > - search-api > - i could not find any documentation about it > ================================ > > the rest: > > - multipleDBsupport > - the wikipage says that the author wants to apply some changes from > the oracle-changes, and only then can/should the testing begin > > - genericAuthorization > - under active development > > > so, in short, the only testable branches seems to be fullHistory and > rowLevelPermissions, and even there it's not clear if they are now > considered done, or still in progress. > > > > so, i think those wikipages linked from > http://code.djangoproject.com/wiki/ActiveBranches should be first > updated, and should contain info about the following: > > - if they are finished (ready for testing) or not > - documentation about how it works. > > because otherwise it's quite hard to test. > > i don't know if we should send mails directly to the authors, or they > are reading django-devel... > > > p.s: as i said, i deeply respect the work of the developers on those > branches. all i wrote was with the goal that we can make the life of the > testers easier => get more testing for the branches => merge the > branches into the trunk > > gabor > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
