[Nix-dev] [call for] Release manager for Hydra

Domen Kožar domen at dev.si
Mon Dec 14 22:41:22 CET 2015


Thanks Christian and Aszlig, I'll talk to you on IRC in a couple of days.

On Sat, Dec 12, 2015 at 12:56 AM, Joachim Schiele <js at lastlog.de> wrote:

> nice to hear that you want to do this.
>
> i've added a documentation about the setup process in the wiki, it can
> be found here:
>
> https://nixos.org/wiki/Installing_hydra_as_nixos_module
>
> On 11.12.2015 12:05, Christian Theune wrote:
> > Hi,
> >
> > ok. I can start with turning this into a checklist in the wiki. After
> > that I’d like walk through those things with someone.
> >
> > Things can take a while currently, as I’m on parental leave. :)
> >
> > Christian
> >
> >> On 08 Dec 2015, at 13:07, Domen Kožar <domen at dev.si
> >> <mailto:domen at dev.si>> wrote:
> >>
> >> Hey Christian,
> >>
> >> thanks. I had following in mind.
> >>
> >> Before the release:
> >>
> >> - check changelog is really up to date
> >> - mark any backwards incompatible changes
> >> - make sure all hydra tests pass
> >> - make sure the upgrade procedure works from previous release
> >> - test that setting up hydra from scratch works by following
> >> installation guide (this could be automated with NixOS test)
> >>
> >> At release time:
> >>
> >> - create a git (annotated) tag
> >> - mark the release date in changelog, etc
> >> - post a mail to nix-dev
> >>
> >> After release:
> >>
> >> - bump the package in nixpkgs
> >>
> >> I'm sure I forgot something, but we should document the process and
> >> improve it as we go.
> >>
> >> PS: we have a similar issue opened for
> >> NixOS: https://github.com/NixOS/nixpkgs/issues/4442
> >> PS: Eelco might know if there is something else that needs to be taken
> >> care of
> >>
> >> Domen
> >>
> >> Domen
> >>
> >> On Tue, Dec 8, 2015 at 12:54 PM, Christian Theune <ct at flyingcircus.io
> >> <mailto:ct at flyingcircus.io>> wrote:
> >>
> >>     Hi,
> >>
> >>     I *might* be able to. But I’m not sure I’m qualified enough. We’re
> >>     using it at the company and rely on it, so this would be a good
> >>     place to contribute back.
> >>
> >>     Anyone willing to detail what is expected regarding QA in a bit
> >>     more detail?
> >>
> >>     Cheers,
> >>     Christian
> >>
> >>>     On 08 Dec 2015, at 12:06, Domen Kožar <domen at dev.si
> >>>     <mailto:domen at dev.si>> wrote:
> >>>
> >>>     So no one is willing to step up? This would benefit the whole
> >>>     community and it's not a lot of work, mostly small housekeeping.
> >>>
> >>>     On Wed, Nov 18, 2015 at 2:26 PM, Matthias Beyer
> >>>     <mail at beyermatthias.de <mailto:mail at beyermatthias.de>> wrote:
> >>>
> >>>         On 18-11-2015 12:23:30, Peter Simons wrote:
> >>>         > Domen Kožar writes:
> >>>         >
> >>>         >  > We need someone to volunteer to be a release manager.
> They would be
> >>>         >  > doing QA that the release works and make sure changelog,
> docs, etc
> >>>         >  > are updated.
> >>>         >
> >>>         > Also, we need a Hydra module for NixOS so that NixOS users
> can set-up
> >>>         > Hydra easily through their configuration.nix file. Hydra
> provides such a
> >>>         > module, of course, but the fact that it's living in a
> separate repository
> >>>         > complicates matters a bit, particularly for newbies who are
> just getting
> >>>         > started and who might try out NixOS mostly because of Hydra.
> We cannot
> >>>         > expect them to mess with imports and fetchgit and channels
> and whatnot on
> >>>         > their first day.
> >>>         >
> >>>
> >>>         Big +1 on this. I'd love to run my own hydra, but the lack of
> >>>         a simple
> >>>
> >>>             services.hydra.enable = true;
> >>>
> >>>         -ish configuration keeps me away from this.
> >>>
> >>>         --
> >>>         Mit freundlichen Grüßen,
> >>>         Kind regards,
> >>>         Matthias Beyer
> >>>
> >>>         Proudly sent with mutt.
> >>>         Happily signed with gnupg.
> >>>
> >>>         _______________________________________________
> >>>         nix-dev mailing list
> >>>         nix-dev at lists.science.uu.nl <mailto:
> nix-dev at lists.science.uu.nl>
> >>>         http://lists.science.uu.nl/mailman/listinfo/nix-dev
> >>>
> >>>
> >>>     _______________________________________________
> >>>     nix-dev mailing list
> >>>     nix-dev at lists.science.uu.nl <mailto:nix-dev at lists.science.uu.nl>
> >>>     http://lists.science.uu.nl/mailman/listinfo/nix-dev
> >>
> >>     --
> >>     Christian Theune · ct at flyingcircus.io
> >>     <mailto:ct at flyingcircus.io> · +49 345 219401 0
> >>     Flying Circus Internet Operations GmbH · http://flyingcircus.io
> >>     <http://flyingcircus.io/>
> >>     Forsterstraße 29 · 06112 Halle (Saale) · Deutschland
> >>     HR Stendal HRB 21169 · Geschäftsführer: Christian. Theune,
> >>     Christian. Zagrodnick
> >>
> >>
> >
> > --
> > Christian Theune · ct at flyingcircus.io <mailto:ct at flyingcircus.io> · +49
> > 345 219401 0
> > Flying Circus Internet Operations GmbH · http://flyingcircus.io
> > Forsterstraße 29 · 06112 Halle (Saale) · Deutschland
> > HR Stendal HRB 21169 · Geschäftsführer: Christian. Theune, Christian.
> > Zagrodnick
> >
> >
> >
> > _______________________________________________
> > nix-dev mailing list
> > nix-dev at lists.science.uu.nl
> > http://lists.science.uu.nl/mailman/listinfo/nix-dev
> >
>
>
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20151214/ebf07f72/attachment-0001.html 


More information about the nix-dev mailing list