What about releases?

142 views
Skip to first unread message

Friedrich von Never

unread,
Nov 16, 2015, 1:09:12 PM11/16/15
to Pash Project
Hello, guys!

Today I'm willing to start making Pash available in form of the Linux package (note that I have no maintainer experience but I want to learn).

Currently I'm using Nixos (a nice modern "pure functional" Linux distro) on some of my computers. Its package repository is Nixpkgs, and I've already managed to create a working package from the current source code of our master branch.

I haven't very much experience maintaining packages, but I think that it would help if Pash had some stable releases (or semi-stable, maybe beta or something... well let's just call them "releases") tagged in git. Then I could point my build scripts to these releases (note that Nixos is a source-based distro almost like Gentoo).

So, what would you say? If we're going to make releases, who will be responsible for that (deciding to make a release, creating the tag on github, pushing it)? What versioning scheme will we use? I'd personally prefer semver.

Also, currently our Releases page contains not very relevant things, we'll need to clean it up a bit.

PS. Also Nixos have the very good first-class support for Mono programs, check the build script. Glorious!

Jay Bazuzi

unread,
Nov 16, 2015, 2:00:07 PM11/16/15
to pash-p...@googlegroups.com

Sure, I say go for it.

As for versioning, I like to keep things as simple as possible. Usually that means whole numbers only (v1, v2, ...). Would that work for us?

-J

--
You received this message because you are subscribed to the Google Groups "Pash Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pash-project...@googlegroups.com.
Visit this group at http://groups.google.com/group/pash-project.

Friedrich von Never

unread,
Nov 16, 2015, 11:36:05 PM11/16/15
to Pash Project
I was planning on making releases often as long as it's not too time-consuming. So these days we'd have a new package every two weeks or so (after every couple of pushes to the master branch). Won't the version be increasing too fast?

By the way, I've read the Nixpkgs documentation and I think it will be okay to use git commit hashes instead of strict versions till we stabilize Pash a bit. So let's discuss a general versioning strategy; no need to hurry. I'll just release a packages versioned by their commit hashes from now.

Jay Bazuzi

unread,
Nov 17, 2015, 10:16:35 PM11/17/15
to pash-p...@googlegroups.com

What is "too fast"? Is there a problem with v100 or v1000 that in not seeing?

-J

Reply all
Reply to author
Forward
0 new messages