Dear all,

As part of the lead-up to the 1.8.0 release, the openafs-stable-1_8_x
branch has been created in Gerrit.  Changes specific to 1.8.x can
be submitted directly against refs/for/openafs-stable-1_8_x, but changes
that are generally applicable should go through master and be cherry-picked
as new commits targetting 1.8.x.  In keeping with our historical policy,
changes aiming to enter openafs-stable-1_6_x should first go to master,
then get cherry-picked successively to openafs-stable-1_8_x and finally
openafs-stable-1_6_x.  Since the 1.8 branch is expected to remain
mostly frozen until the final 1.8.0 release except for bugfixes and
new OS support, the release team may be willing to grant exceptions
on a case by case basis.  However, as 1.8.x becomes the new stable
release branch and 1.6.x transitions to the legacy release branch, it
is expected that the pace of change on openafs-stable-1_6_x will reduce
naturally as well.

The master branch will be gradually opening up for new development in
the coming weeks, though we should generally try to avoid sweeping
changes until after the 1.8.0 release is finalized, to facilitate
propagating patches through master to openafs-stable-1_8_x.  There
is quite a backlog of changes reviwed "-2 not for 1.8", and it will
take quite some time to go through them all again and consider them
anew for inclusion in master -- please feel free to comment on particular
changes if you think they should be prioritized or deprioritized for
that process.

Thanks to all who helped work towards resolving the issues raised with
1.8.0pre1, and here's to having a great 1.8.0 release!

OpenAFS-devel mailing list

Reply via email to