From: Jeremie Dimino <jdimino@janestreet.com>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: [Caml-list] More frequent pushes to Jane Street github repositories + janestreet/opam-repository
Date: Mon, 23 May 2016 10:39:53 +0100 [thread overview]
Message-ID: <CANhEzE4xNut=+vYcd+0k4vuQ=6k5WN9BWkvvygRuDXo-1zQp7g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1797 bytes --]
Hi,
We are currently trying to improve our workflow for releasing our code on
github and following up on external contributions.
As a first step in this direction, we reworked our internal process for
exporting the public release and we are now able to push to github more
often. So going forward, instead of pushing one huge commit before every
major release in the main opam repository, we will push smaller commits
more frequently.
This has several consequences:
- it will be easier to follow the latest changes
- accepted pull requests will appear in the git repository earlier
- you can complain if we break your code before the next release in opam...
Initially the commit messages will still be meaningless and the changelogs
might be slightly lagging behind given that producing them still requires a
fair amount of work from a human. However, we are planning to improve this
over time.
Note that we'll continue to provide support for the latest version that is
released in opam.
## janestreet/opam-repository
To help trying the development version of our libraries, we've setup an
opam repository that follows their latest development version [1]. So in
order to try out the latest version of core, you can do:
$ opam repo add git://github.com/janestreet/opam-repository.git
$ opam install core
Pinning individual packages with `opam pin add --dev` might work as well,
but there is no guarantee about it.
## 113.43+70
To start the new process, we just pushed the latest version of our code on
github. The version is 113.43+70 and includes a fair amount of changes.
[1] https://github.com/janestreet/opam-repository
--
Jeremie Dimino, for the Core team
[-- Attachment #2: Type: text/html, Size: 2296 bytes --]
reply other threads:[~2016-05-23 9:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANhEzE4xNut=+vYcd+0k4vuQ=6k5WN9BWkvvygRuDXo-1zQp7g@mail.gmail.com' \
--to=jdimino@janestreet.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox