[SAMBA4] Time for another tech preview?

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tridge at samba.org wrote:
> Jerry,
> 
>> I think you might have some misconceptions of Samba 4.
>> Samba 4 is architecture and technology.  The name is
>> slightly misleading in that it implies that this particular
>> code base will become the successor to the current Samba
>> 3.0.x releases.  It would have been better to give it a
>> code name rather than a numeric release. But that is all
>> in hindsight.
>
> I think perhaps you have read more into the research 
> tag than I intended. When I described Samba4 as a
> research branch, I said:

Hey Tridge,

I think you have to take the thread in context.
Rod was asking about whether or not the next TP
would be close enough to the final release that
he could write about it.  My gut is that our final
releases are always different enough from pre-releases
to invalidate documentation.  And developers should
be given that freedom so I have no problem with it.

We've had this discussion before and we both understand
the relationship between the branches.  We've agreed
on it.  We talked on the phone about it.  We talked about
wanting to eventually be back in one branch.  What I said
is my personal official answer to how Samba 4 relates
to the current and future Samba releases.  It's the exact
same thing I've been saying since Samba XP.

What specifically did I say that you don't agree with?
If it's the release number comment, then fine.  I'll
withdraw that.

> So I do want to see a Samba 4.0 release happen, 
> and I expect that release will have a lot in
> common with the current SAMBA_4_0 branch.

Not from a writer's perspective IMO.  Every little thing
matters.

> I think another TP is a good idea, and you are 
> dead right that people should not look at the TP and
> go "oh no! Samba is abandoning printing!".

I never disagreed with another TP.  I was writing to
Rod's original question about a final release and when
it would be stable enough (in the sense of configuration
steps and feature steps).





cheers, jerry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFHa5EIR7qMdg1EfYRAnLdAKDKXuGmC+yDpMN7PKFzR17sT+E5IgCfQUY0
895zo7Evsd6SYXGI6n/WRDM=
=YSL2
-----END PGP SIGNATURE-----