<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 05/ 9/16 12:08 AM, Aurélien Larcher
wrote:<br>
</div>
<blockquote
cite="mid:CAHMq6q3FhSfiAmoZ-GydCr3qMYDwyuodU-PPmfc9YNjCY6zebg@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote"><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class=""><br>
</span> There is nothing like "legacy release". Bad
choice if wording.<br>
/legacy (<a moz-do-not-send="true"
href="http://pkg.openindiana.org/legacy"
target="_blank">pkg.openindiana.org/legacy</a>) holds
opensolaris releases up tp snv_134 and that is what
Legacy is.<br>
<br>
You are referring to Openindiana /dev development
releases.<br>
</div>
</blockquote>
<div><br>
</div>
<div>Like it or not, something dead for 2 years and
unmaintained maybe called "legacy" but I can use "vintage"
if you like.<br>
</div>
<div>I can also call it "Château OpenIndiana 2013 Vendange
Tardive" or whatever, does not change the current
developments.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
It is about precising what is named what. <br>
Not looking what is active and how long and how.<br>
<br>
You can't call /dev past development releases a "Legacy" since
"Legacy" is reserved for /legacy and they are Opensolaris dev.
releases.<br>
<br>
It's not about what is active or, not, we all know only OI hipster
is currently active it is simple you can't just decide to change
/dev's name because you say so, <br>
because you create conflict of naming that creates confusion for
users and documentation.<br>
<br>
I don't find this humorous , I understand you recommend that
Openindiana development releases in /dev be called "Vintage
releases".<br>
I don't think that is more appropriate to call it "Old Openindiana
/dev development releases" and naming it wit any new name including
one you proposed, would create confusion and disable /dev renewal.<br>
<br>
<blockquote
cite="mid:CAHMq6q3FhSfiAmoZ-GydCr3qMYDwyuodU-PPmfc9YNjCY6zebg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> <br>
Openindiana is currently not devided into anything, and
there is no devision between openindiana and
Openindiana, so it is again bad choice of wording.<br>
Since only Openindiana Hipster is updated regularly, it
is what is obviously active, so there is nothing like
division in Openindiana.<br>
</div>
</blockquote>
<div><br>
</div>
<div>Moving from consolidations to oi-userland, dropping
legacy and obsolete components, moving away from SUN
compilers etc... make 151a and Hipster two different
animals.<br>
</div>
<div>Additional philosophical questions: if a tree has
several branches, is it divided ? does your self from 3
years ago identifies with your current self ? etc...<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Openindiana is not divided. That is bad choice of words that sends
the wrong message.<br>
Think about what people from outside think when they hear the world
"Devided", they simply won't get it.<br>
<br>
Openindiana /hipster just continued to be active somewhere when OI
/dev stopped being active, nothing is "devided" in Openindiana, how
many projects or releases does it have.<br>
<br>
This is a practical thing.<br>
You have cow and a pig. You decided to call a cow as a pig, because
a cow didn't give you milk lately. <br>
That is wrong, because pig is a pig and cow is a cow. (and neither
cow is a sheep)<br>
It's an old cow.<br>
<br>
You can't call /dev other then "Old development releases", because
"Legacy" is reserved and used already.<br>
<br>
<blockquote
cite="mid:CAHMq6q3FhSfiAmoZ-GydCr3qMYDwyuodU-PPmfc9YNjCY6zebg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> <br>
I think that plans of putting releases that could land
in /dev out of Hipster snapshot (after testing is made
with updating) , could be hurt, if you call Openindiana
development releases in /dev with the wrong name.<br>
</div>
</blockquote>
<div><br>
</div>
<div>If you want to call "Development", something that is
not developed, fair enough: come up with a better
taxonomy, I have personally no strong opinion.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Development releases are both in /dev and /hipster now in past and
in the future.<br>
<br>
I think that it is sane plan to update contents on /dev with new dev
release, made out of /hipster, <br>
but you should stop calling /dev with the other name, including docs
and mentions on site.<br>
<br>
<blockquote
cite="mid:CAHMq6q3FhSfiAmoZ-GydCr3qMYDwyuodU-PPmfc9YNjCY6zebg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>I propose "vintage", "indie" and "hipster" to stay
rock'n roll.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Vintage is not good because /dev will stay /dev, yust updated with
hipster snapshots.<br>
That would allow that /dev people can see one day update notice.<br>
<br>
Vintage as a name dosn't have any use at the moment and it would be
too complicated to have and maintain transition period and explain
that "vintage" is a /dev again.<br>
It is mostly useless from all usage point to make a new name for
/dev - old development releases.<br>
<br>
I already mentioned that it would hurt /dev landing effort and
create confusion, so please don't re-use "legacy" as a name and
remove wrong references that include it and do not use proposed
"vintage" as it is not accurate and also creates confusion.<br>
Only option that is accurate now and in the past and will be in the
future is "old development releases" (untill they are renewed).<br>
<br>
<blockquote
cite="mid:CAHMq6q3FhSfiAmoZ-GydCr3qMYDwyuodU-PPmfc9YNjCY6zebg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div> <br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> <br>
Also if you have a separate announcement not related to
the topic can you please make a new topic on ML whe
nposting separate topic?<br>
</div>
</blockquote>
<div><br>
</div>
<div>I updated the page to point to MATE's Wiki page
according to Ken's message so my reply is in no way
unrelated.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Maybe I wasn't clear enough.<br>
I was thinking that you should make new topic on mailing list when
you anounced "roadmap page" update, because it is not directly
related to MATE test build announcement (clearly not related to
Mate).<br>
That way it could be better noticed and not overlooked in different
topic.<br>
<br>
</body>
</html>