List for cgit developers and users
 help / color / mirror / Atom feed
From: dlcampbell at gmx.com (Daniel Campbell)
Subject: Release plan for 1.2
Date: Tue, 03 Jul 2018 21:56:46 -0700	[thread overview]
Message-ID: <F0562796-E5A2-437A-8B48-7AE4756F8863@gmx.com> (raw)
In-Reply-To: <CAHmME9qgyQx8RGQ7dkD43MdV9Xa00CXgUOf6QKc2iefBkzwOhw@mail.gmail.com>

Sounds pretty exciting. The recent activity on the ML is lively and interesting to read and learn from. Keep up the great work! Maybe some day I'll try hacking on it. :)

On July 3, 2018 6:23:22 PM PDT, "Jason A. Donenfeld" <Jason at zx2c4.com> wrote:
>Hey guys,
>
>Seeing as there hasn't been a release for a while, it seems prudent
>that we get one out fairly soon. Indeed there have been a lot of new
>things added and code refactored since 1.1. There's still the
>possibility of getting the render view improvements ready for 1.2 --
>if those are resubmitted according to the plan John and I discussed --
>but I'm also fine putting these off until after, as we've got quite a
>bit of churn with 1.2 as-is.
>
>Either way, kernel.org's Konstantin is back next week, at which time I
>expect he'll give the new archive signature notes feature a spin, and
>if it works as intended, I think I'll release shortly after. Between
>now and then, that leaves us some time for refining things as they
>come up.
>
>How's that sound to everyone?
>
>Jason
>_______________________________________________
>CGit mailing list
>CGit at lists.zx2c4.com
>https://lists.zx2c4.com/mailman/listinfo/cgit

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.


  reply	other threads:[~2018-07-04  4:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04  1:23 Jason
2018-07-04  4:56 ` dlcampbell [this message]
2018-07-04  5:58 ` list
2018-07-13 20:12 ` konstantin
2018-07-13 20:32   ` Jason
2018-07-13 20:43   ` list
2018-07-13 21:01     ` konstantin
2018-07-25 10:06   ` list
2018-07-25 13:15     ` konstantin

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=F0562796-E5A2-437A-8B48-7AE4756F8863@gmx.com \
    --to=cgit@lists.zx2c4.com \
    /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;
as well as URLs for NNTP newsgroup(s).