Daniel Shahaf wrote: > RFC: > > * Remove revprops.db code from trunk and 1.7 > * Release 1.7 with FSFS f4 > (this is the format that 1.6 used) > * Implement revprops packing in f6 and release that in 1.8
+1. - Julian > This has seen some support on IRC, posting here for objections. > > > >Subject: [Issue 3944] redefine revprop handling in FSFS f5 (creating FSFS > > f6) > > > > ------- Additional comments from [email protected] Thu Jul 7 14:37:24 > > -0700 2011 ------- > > I'm moving this to 1.8, since the design discussions don't seem to keep > > springing new ideas and no > > one wants to redesign the FS under time pressure and release it a week > > later. > > > > In the meantime the thread has grown with several suggestions (some of > > which should be > > implemented), and design and implementation have started on the > > revprop-packing branch. > > > > In the meantime, I'll open a new issue to rip out FSFS f5 from trunk. (The > > new code will be called f6.) > > That's all we need to do prior to 1.7.0. > > > > ------------------------------------------------------ > > > Subject: [Issue 3952] New - rip out FSFS SQLite-based revprops code (f5) > > > > ------- Additional comments from [email protected] Thu Jul 7 14:41:32 > > -0700 2011 ------- > > See issue #3944. > > > > Currently (f5) FSFS packs revprops into SQLite. We want to redesign that > > (calling the new design f6), > > but we don't have time for that before releasing 1.7.0. As an interim > > solution, this issue calls for > > removing f5 from trunk, releasing 1.7 with f4 (the same as in 1.6). > > > > Looking forward, issue #3944 calls for of designing and releasing f6 in 1.8. > > > > Format 5 will remain unsupported into the future; repositories that use it > > (created by 1.7-dev) will > > have to be dump/loaded using trunk/1.7.0-alpha3 code. A tools/ scripts to > > upgrade/downgrade f5 > > into f4 or f6 may be written in the future. > > > > ------------------------------------------------------
