[oi-dev] Release engineering // planing

[ken mays]

Hi Udo,

Jon Tibble takes care of the release.

The oi-userland is nearing update completion to the s12-23 upstream specs. I've mapped out the s12-26 update specs on the Wiki.

Give it some time... a few important bugs need ironing out as well.

~ Ken





________________________________
 From: Udo Grabowski (IMK) <udo.grabowski at kit.edu>
To: OpenIndiana Developer mailing list <oi-dev at openindiana.org> 
Sent: Monday, July 15, 2013 12:29 PM
Subject: Re: [oi-dev] Release engineering // planing
 

On 15/07/2013 16:14, Andrzej Szeszo wrote:
> Hi All
>
> At least for now, /hipster contribution process should stay as it is:
> pull requests/direct commits to the github repo. The team is too small
> to consider any other options at the moment in my opinion.
>
> I reckon /dev can stay as it is now as well. Jon Tibble is working on
> getting the repo updated. When he's done, the update should not break
> thousands of existing OI installations. There is a risk of making many
> users unhappy if we were to use /hipster repo to replace /dev.
>
> People who are interested in stable release are generally using OI on
> the servers. I think future formal hipster-based OI releases could
> have packages split into two sets. The "core" one and the "all the
> rest" one. Let's learn from the mistakes made in the past and
> successes of the other distros and make supported "core" package set
> small (additional packages supported on best effort basis).
>
> Also, it would make a lot of sense to have per-release repositories,
> like pkg.openindiana.org/<something>/<"core"> and
> pkg.openindiana.org/<something>/<"all the rest">. "something" could be
> release codename, date tag, some version number, etc. It would make it
> easier to manage things that way. Repos would update quicker, mirrors
> would be easier to create and be smaller. It would prevent users from
> accidentally replacing all of their system files each time new release
> is made (in case of publishing each release to /stable, we have BEs,
> but still...). It would be easier to get rid of old unsupported
> releases going forward. Also, pkg5 solver would have less metadata to
> deal with and would work faster!

This is totally confusing. Is there a release, and when and where
will it happen ? Sounds like hipster is sometimes doing a release,
but dev/ (aka Ken) does this also. Or is hipster a ever changing
sandbox without release ? For what ? Sounds like alll responsibility
for making something stable should be laid on Ken's shoulders
picking the right pieces from hipster to put it into /dev to ever
get someting useful from hipster.

And no, there are indeed people outside who regularily use more
than "core" (whatever that means, there are more than enough "cores"
outside, we don't need another)...
-- 
Dr.Udo Grabowski    Inst.f.Meteorology a.Climate Research IMK-ASF-SAT
www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology            http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany  T:(+49)721 608-26026 F:-926026

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20130715/ea08b2fd/attachment-0005.html>