RE: [ZODB-Dev] RE: RE: RE: RE: PersistentMapping
[Thomas Lotze] > Maybe it's not all that obvious in this case: NEWS.txt on the 3.5 branch > is talking about a 3.5.1b3 release which, according to the existing tags > and the NEWS.txt on the 3.5.1 tag, never happened. Should the concerned > changes be re-labelled 3.5.2b1? Good eye! That looks right. It appears I plain forgot that 3.5.1 final had already been released when the two "3.5.1b3" entries got added, so wrote the blurbs as if they _would_ appear in 3.5.1b3. Such things happen when you're juggling half a dozen branches; for penance, I'll fix this one ;-) ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
[ZODB-Dev] RE: RE: RE: RE: PersistentMapping
Tim Peters wrote: > - Edit NEWS.txt by hand, inserting branch-appropriate NEWS for what > changed in the rest of the merge. Usually this amounts to just > copying paragraphs from one NEWS.txt to another, changing version > numbers in an obvious way. Maybe it's not all that obvious in this case: NEWS.txt on the 3.5 branch is talking about a 3.5.1b3 release which, according to the existing tags and the NEWS.txt on the 3.5.1 tag, never happened. Should the concerned changes be re-labelled 3.5.2b1? -- Thomas ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
[ZODB-Dev] RE: RE: RE: RE: PersistentMapping
Tim Peters wrote: > The best idea is to clean it up so that it makes good sense. There's > lots of historical cruft in the ZODB code base that doesn't make much > sense anymore. Hm. To me, this would mean to get rid of the test suites in src/ZODB/tests and move checks which they do but the test suites in src/persistent/tests don't do to the latter. I'll have a go at that later in the week. > "Old" news will become "new" news again, when the next micro release > in the ZODB 3.5 line is made. Oh, I meant "old" as in "telling about old changes", not "having been read a long time ago". > BTW, merges to NEWS-like files generally don't work well across > branches. What to do instead: > > - Do the merge. > > - Do "svn revert NEWS.txt" to throw away the botched merged on that > single file. > > - Edit NEWS.txt by hand, inserting branch-appropriate NEWS for what > changed in the rest of the merge. Usually this amounts to just > copying paragraphs from one NEWS.txt to another, changing version > numbers in an obvious way. That's what I'd do after thinking about it some more, anyway. -- Thomas ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
[ZODB-Dev] RE: RE: RE: RE: PersistentMapping
Christian Theune wrote: > The whole testing story together with all the active branches and > platforms sounds like we want to have some buildbot clients for ZODB as > well. I could set up a buildbot client on Windows 2k and Linux to test > various ZODB branches ... > > That could be added to the Zope buildbot then ... Any oppinions? I could also offer my buildbot slave on a Linux 2.4 Debian testing if that's of any interest. It's currently running tests for the Zope3 trunk. -- Thomas ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
