On Thu, Dec 6, 2018, at 1:17 PM, Matthew Ahrens wrote:
>> 
>> One thought would be:  As a delivery vehicle drops out of support we
>> can remove it from the list.  So say we have -o features=portable
>> include Ubuntu 16.04 LTS.  When support for Ubuntu 16.04 LTS expires
>> we remove it from the portable list.  Now, that directly contradicts
>> the first pass at this.  For instance FreeBSD (and FreeNAS) 9.3-R
>> have long been out of support by the "vendor"> 
> I think that's a very conservative way to define it - essentially: you
> "portable means you can take this pool to any FreeBSD or Ubuntu that's
> supported by the vendor".  I would suggest we look at it from the
> other direction: "portable means that there's some version of FreeBSD,
> ZoL, and illumos that you can take your pool to".  More specifically
> we could say "it's in a released version of FreeBSD (e.g. FreeBSD
> 11.1), a released version of ZoL (e.g. Zol 0.7.2), and in the illumos
> master branch" (since there's no "releases" of illumos).  That said,
> I'm open to variations on this (e.g. should we say it's in a SmartOS
> release rather than illumos master?  Or it's in FreeBSD-STABLE vs a
> numbered release?)> 
> --matt
> 

I'll make two assertions here:

1) features=portable is intended towards users
2) users by definition use releases.  freebsd stable branch, master,
   head, I built my own kernel from a checkout...those are all things
   done by !users.
So what if we amend the proposal to say there are multiple
portable levels:
Forgive the horrible names, we'll need real names that are the moral
equivalent  on my horrible names:
features=portatblenow (able to import on any contemporary tier 1
platform)features=portablesupport (able to import on any tier 1 platform still
under support (or a specific date if we want to use dates)) 
[1]features=maxportible (A very limited subset of features that enables
maximum cross platform support)features=none (Ultimate portability)

[1] I'm keen on supported releases because that's what users use.

--

Thanks,

Josh Paetzel



------------------------------------------
openzfs: openzfs-developer
Permalink: 
https://openzfs.topicbox.com/groups/developer/T562a2f6ecf883736-M9923a76123ee2e9f26e39454
Delivery options: https://openzfs.topicbox.com/groups/developer/subscription

Reply via email to