| From: | Sehrope Sarkuni <sehrope(at)jackdb(dot)com> |
|---|---|
| To: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Release schedule |
| Date: | 2015-08-05 11:37:52 |
| Message-ID: | CAH7T-apKqUS5CQDy7NtnXqWGOp3sqkeUyPHQ_SH+_emyKD9vgQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
(note: resending as I forgot to cc the list)
Running something like this should give you a decent start:
git log REL9_4_1201..HEAD | grep -E 'feat:|fix:|perf:|docs:|chore:'
I'm not sure if it'll catch everything though as there's probably some
commits that aren't tagged like that.
Going forward if we're sticklers about enforcing the commit guidelines[1]
at commit and/or merge time, I think we can fully automate this for
subsequent releases.
[1]: https://github.com/pgjdbc/pgjdbc#-git-commit-guidelines
Regards,
-- Sehrope Sarkuni
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dmp | 2015-08-05 15:57:24 | Re: Release schedule |
| Previous Message | Vladimir Sitnikov | 2015-08-05 11:35:32 | Re: Release schedule |