Release Plans

[Atish Patra]

On Mon, Oct 25, 2021 at 2:52 AM Bin Meng <bmeng.cn at gmail.com> wrote:
>
> On Mon, Oct 25, 2021 at 4:19 PM Anup Patel <anup at brainfault.org> wrote:
> >
> > On Thu, Oct 14, 2021 at 3:05 AM Atish Patra <atishp at atishpatra.org> wrote:
> > >
> > > On Wed, Oct 13, 2021 at 5:41 AM Alexandre ghiti <alex at ghiti.fr> wrote:
> > > >
> > > > Hi Anup, Bin,
> > > >
> > > > On 10/13/21 9:48 AM, Bin Meng wrote:
> > > > > Hi Anup,
> > > > >
> > > > > On Wed, Oct 13, 2021 at 2:03 PM Anup Patel <anup at brainfault.org> wrote:
> > > > >> Hi Jessica,
> > > > >>
> > > > >> On Wed, Oct 13, 2021 at 12:56 AM Jessica Clarke <jrtc27 at jrtc27.com> wrote:
> > > > >>> Hi,
> > > > >>> The latest OpenSBI release is 0.9 from January. With SBI 0.3(.1) on the
> > > > >>> way and Unmatched support added since then, are there plans for a new
> > > > >>> release any time soon? We’d like to have a newer version in the FreeBSD
> > > > >>> ports tree so we can more easily provide updated firmware to Unmatched
> > > > >>> users.
> > > > >> Next release will be OpenSBI v1.0 (having SBI v0.3 implementation) and
> > > > >> we can target this sometime in Nov 2021.
> > > > > If possible can we release OpenSBI v1.0 before QEMU 6.2.0 soft freeze
> > > > > (Nov 02) or hard freeze (Nov 09) so that it can be integrated into
> > > > > QEMU 6.2.0.
> > > > >
> > > > >> We wanted to make SBI v0.3 fully stable for existing boards (particularly
> > > > >> SiFive unmatched) before releasing OpenSBI hence the delay. We are
> > > > >> almost there with few pending changes for SBI PMU and reset driver
> > > > >> improvements.
> > > > >>
> > > > >> Post OpenSBI v1.0 release, we want to have more predictable release
> > > > >> cycles (which we will document as well). I would like to have a release
> > > > >> cycle which is realistic and agreed by most people over here.
> > > > > Agree.
> > > > >
> > > > >> Thoughts or Suggestions ??
> > > > > I suggest we align this with QEMU release cadence for easier
> > > > > integration with QEMU. +Alistair Francis
> > > >
> > > >
> > > > I think lots of bigger projects depend on openSBI (ex: QEMU 4-month,
> > > > Ubuntu 6-month, Fedora 6-month) and to accommodate them all, taking a
> > > > rather quick release cycle could be interesting: 2-3 months :)
> > >
> > > It all depends on how many features we add to OpenSBI in 2-3 months.
> > > We definitely added
> > > enough features to warrant a release. We are just waiting for SBI
> > > specification to be called frozen
> > > as per the oficial process[1] which was defined recently.
> > >
> > > [1] https://docs.google.com/document/d/1A4gZlXXFT_a9QGzlc9g2RHg853e6ZDB59coANEYN3Aw/edit
> >
> > Based on experience till now, I am leaning towards a half-yearly release
> > cycle. Past few years, we were releasing OpenSBI quite frequently but
> > sometimes releases had below 50 commits.
> >
> > I suggest that every year we release in June and December. Also,
> > to do a release we should require at least 50 commits. In future, if
> > commit rate increases then we will move to 3-releases per-year (i.e.
> > every 4 months).
> >
> > Does this sound okay ??

Works for me.

Additionally, we want to bring up another topic. We think the OpenSBI
project has grown
big enough to have a logo :). Any simple logo that represent some of
the traits i.e. RISC-V, SBI and OpenSource
would be wonderful. We think crowdsourcing is the best option given
that it's a community project.
It is needless to say that the proper credit will be given to the
person coming up with the best logo.
We can start a crowdsource contest with a prize (may be a RISC-V board
or something else) as well to attract
more entries.

Any other ideas to attract more entries or suggestions for a logo?

>
> Sounds good to me. Thanks.
>
> Regards,
> Bin



-- 
Regards,
Atish