Hi,

> Realistically forking from the ON gate is not really an option IMHO.

  That's not actually what I was asking, although I agree with your
  conclusion about a source fork.

  The real point is whether or not Indiana might choose to skip a
  delivery of a consolidation because it felt it was of insufficient
  quality, relative to the other goals it has for a particular release.
  For ON, this could happen during the periods intermediate to a
  multi-phase project integration.

Ah, now I see, thats a very different scenario, and one which requires
a lot more consideration and thought.

What really needs to be defined here is

1. What exactly is going into a release
2. What is the acceptable level of qa and quality
3. What is an acceptable level of soak time

and if something fails on one of these critera should it then be
removed from release X, and slated for inclusion in X+1? Is this
somewhat closer to what you were asking?


> >  - How do you see uname(1)'s output changing from Indiana release to
> >    Indiana release?
>
> A suggestion
>
> sysname - IndianaOS
>
> release - 1.0
>  increment in .1 by 6 monthly release until some milestone is marked by the
>  communtity - the start with 2 etc.
>
> version - ind_01, ind_02 etc
>   no really any different to on.
>
> but I fail to see how this is important in deciding how often indiana
> should have a milestone release. Just hardcode vers.c for the first
> build and move on from there. Versioning needs to be defined, just not
> at the moment - defining what indiana actually is seems somewhat more
> important.

  If you would prefer that I table my questions due to other project
  priorities, that's fine.


Its really not up to me, its the community, naming and versioning is
an important issue, but its not the most pressing at the moment -
which is the point I was trying to make.

To be honest though I'm confused as to what is pressing.

- Fintan
--
Blog - http://fintanr.journalspace.com
Work Blog - http://blogs.sun.com/fintanr
_______________________________________________
indiana-discuss mailing list
[email protected]
http://opensolaris.org/mailman/listinfo/indiana-discuss

Reply via email to