Yes, and I've agonized over this very possibility. Maybe the thing
to do is to poll the people on kernel@. HAMMER won't be ready for
sure (things take however long they take), but the hardest part of it
is working and stable and I'm just down to garbage collection and
crash recovery. Crazily enough, that is what all the major surgery
yesterday, and the continuing work, is about.
So what do people think? Should this month's release be 1.12 or 2.0 ?
-Matt
Matthew Dillon
<dillon@backplane.com>I'd go with 1.2 for now. A nice, known-stable release with an experimental feature which isn't quite ready yet. And then release 2.0 with HAMMER known to be good, solid, and well-tested. If you're going to make a big deal about HAMMER, then it would be doubly-plus-good to be confident that all the pieces of it have seen some stress-testing. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Too bad we can't reuse version numbers ;).
--
Thomas E. Spanjaard
tgen@netphreax.netI'd vote 1.12 Save up 2.0 for a really big milestone.
Make this a 1.12, because HAMMER is only in an alpha state. Then when HAMMER is production ready release, change the numbering scheme altogether. The roman numerals for example are nice, and would attract attention. DragonFly XIII sure looks good, and the june release DragonFly XIV. Maybe dump the odd-even numbering altogether. Petr
Whatever else is decided, as one saddled with a roman numeral surname suffix these past 63 years, I'm dead-set against those! Give a thought to my numerous Irish friends, who casually drop 'aitches', and what happens to 'William B Hacker III'. ;-) - and fast forward with 'X' = [unknown | mystery], and find XIII == 'DragonFlyBSD's [unknown | mysterious] turd release' There's gotta be a better way? Bill
1.12 -- Robert Luciani Chalmers University of Technology, SWE Department of Computer Science and Engineering http://death.olf.sgsnet.se:8080/public.key
1.12 -- System Programmer -- I'm Searching For Perfection, So Even If U Need Portability U've To Use Assembly ;-) -- http://libosdk.berlios.de
I'm for 1.12. Joe
I prefer 1.12 Best Regards, sephe -- Live Free or Die
If we want to release 2.0 as the big feature[tm] release, we should go with 1.12, although I don't like the 1.x thing. If 2.0 should be a release with HAMMER as pre-alpha version, we could go with 2.0. I would vote for 2.0 Matthias
With that choice, I'd go for 1.12, but then our __Version is totally broken. Hasso's 2.2 isn't bad either, fooling people nicely :) I'd actually drop the "1." completely, and make it 12-RELEASE, followed by 13-DEVEL. I mean, what constitutes "enough" change to go from 1.* to 2.*, then to 3.*, etc.? That's quite arbitrary. Dropping that digit would avoid that alltogether. Not an easy decision... cheers simon -- Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Simon 'corecode' Schubert wrote: This way we'd obviously have the highest version number of ALL open source OS'es, clearly demonstrating superiority and advancednessitude!
DragonFly XIII-DEVEL
--
Thomas E. Spanjaard
tgen@netphreax.netEven better :) -- Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Neither. 1.2X wherein HAMMER fs is 'experimental' - With an allowance for 1.3X and HAMMER fs 'stable' (as in does not break, crash the OS, or lose data) if not yet fast. Let us not have a parallel to Reiserfs troubles. I'd like to see 2.0 reserved for 'ready for prime time'. i.e. industrial strength stability if not (yet/ever) a speed champ on fs or SMP issues. JM2CW - but we are having to convert servers from <another>BSD to <a different>BSD 'coz - for servers - performance can be addressed with hardware. Stability only with hours of our lives. And we grow weary of chasing fragile patches. Bill
I want 2.0 to have a significant user-visible change to match the major revision, and HAMMER seems to be that thing. Do we need another 6 months to reach that point? I say "2.0", if people can use HAMMER's features, even if it has bugs or stability issues; people (ahem) hammering on it is the best way to test when it's something so basic as a file system. Have we ever established what the criterion are for declaring HAMMER ready for release?
For the most part, I don't really care about version numbers and people's alleged expectations. So I wouldn't object to 1.12 if you don't feel that HAMMER's current status meets the goals set for 2.0. Sascha -- http://yoyodyne.ath.cx
I vote for 2.0rc1. I've watched both Linus and BillG+UncleFester go through many release cycles over the years, and I'd hate to see DragonFly duplicate the Windows Vista debacle just to meet an arbitrary/imaginary deadline. Bill has made billions by promising products he can't (and doesn't) deliver, but those good-ole-days seem to be over now, thankfully!
I don't really care about version number marketing and I don't think that it matters at all. Therefore I think that upcoming stable release should be 2.2 already :). But whatever decision will be, I wish that __DragonFly_version would make logical sense again. -- Hasso
1.12.
--
Thomas E. Spanjaard
tgen@netphreax.net
| Greg KH | [RFC] kobject and kset core changes and cleanups |
| david | Re: [PATCH 0/2] Kexec jump: The first step to kexec base hibernation |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Michael-Luke Jones | JFFS2 using 'private' zlib header (was [RFC] LZO de/compression support - take 6) |
git: | |
| Francis Moreau | Track /etc directory using Git |
| Shawn O. Pearce | libgit2 - a true git library |
| Jon Smirl | ! [rejected] master -> master (non-fast forward) |
| Alexander Gladysh | [Q] Encrypted GIT? |
| Nuno Magalhães | Can't scp, ssh is slow to authenticate. |
| GVG GVG | ssh_exchange_identification: Connection closed by remote host |
| Christopher Bianchi | How can i boot a bsd.rd from windows 2000 ? |
| Richard Stallman | Real men don't attack straw men |
| Eric W. Biederman | [PATCH 0/10] sysfs network namespace support |
| John P Poet | Realtek 8111C transmit timed out |
| KOSAKI Motohiro | [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
