Release schedule and stable releases

[Thomas Haller]

On Thu, 2015-03-12 at 11:52 -0700, Cong Wang wrote:
> Hi, Thomas

Hi Cong,


> What is your schedule for the 3.2.26 release? We are waiting for it as
> we need some new API's. :)

Last week I sent out 3.2.26-rc1. Only wait whether an issue shows up.
Usually ~2 weeks for -rc1.


> Also, there seems no stable release like 3.2.25.x? Commits like
> "idiag: fix out of bound error parsing idiag messages" really deserves
> a stable release, since there are more than 6 months between 3.2.25
> and 3.2.26 releases.

libnl3 never had minor releases... I think what is a good way to manage
releases for large projects (e.g. for the kernel), is not necessarily
best for libnl3.


I will do more often major releases whenever something important shows
up or when somebody here asks me for a new release (*hint*).


For a downstream package maintainer it's hard to asses which patches
should be backported. A minor release would highlight that there is
something important/new.
But instead, I added a git-note refs/notes/release-notes to highlight
important patches that should be backported.

I will mark commits there (for the future). When new important patches show up,
I will send an email to the mailing list to notify downstream package maintainers
that there is something to backport.

Only question is, which commits should be marked as "backport". But that
problem is largely the same as which commits to cherry-pick for
backporting. Pointer from anybody welcome.


how does that sound?



Thomas







The release-notes git-notes:

  git fetch origin refs/notes/release-notes:refs/notes/release-notes

  # all commits with release-notes attached
  git log --decorate --oneline --no-walk \
      $(git tag -l) \
      $(git notes --ref refs/notes/release-notes list | awk '{print $2}')

  # commits marked for backporting
  NOTES_ALL=$(git notes --ref refs/notes/release-notes list | awk '{print $1}' | sort | uniq)
  NOTES_BACKPORT=$(for N in $NOTES_ALL; do git cat-file -p $N | grep -q backport && echo $N; done)
  COMMITS_BACKPORT=$(for N in $NOTES_BACKPORT; do git notes --ref refs/notes/release-notes list | sed -n "s/^$N //p"; done)
  COMMITS_REFERENCED=$(for N in $NOTES_BACKPORT; do git cat-file -p $N | sed -n 's/.*\<\([0-9a-f]\{40\}\)\>.*/\1/p'; done)
  git log --notes=refs/notes/release-notes --decorate --oneline --no-walk \
      $(git tag -l) \
      $COMMITS_BACKPORT \
      $COMMITS_REFERENCED


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/libnl/attachments/20150313/cd898a03/attachment.sig>