hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Dimiduk <ndimi...@gmail.com>
Subject Re: ASF git repository policy update
Date Wed, 13 Jan 2016 16:54:45 GMT
ACK

On Wednesday, January 13, 2016, Sean Busbey <busbey@cloudera.com> wrote:

> no, definitely not. the "rel" space is reserved for PMC-approved releases.
> There's no foundation-backed need to preserve candidates that didn't get
> approved.
>
> On Wed, Jan 13, 2016 at 9:32 AM, Nick Dimiduk <ndimiduk@gmail.com
> <javascript:;>> wrote:
>
> > Should we be pushing RC tags into the rel space as well as release tags?
> >
> > On Tuesday, January 12, 2016, <larsh@apache.org <javascript:;>> wrote:
> >
> > > +1
> > >
> > >
> > >       From: Enis Söztutar <enis@apache.org <javascript:;>
> <javascript:;>>
> > >  To: "dev@hbase.apache.org <javascript:;> <javascript:;>" <
> dev@hbase.apache.org <javascript:;>
> > > <javascript:;>>
> > >  Sent: Monday, January 11, 2016 11:17 AM
> > >  Subject: Re: ASF git repository policy update
> > >
> > > +1 on re-tagging releases under rel/ and using it going forward.
> > >
> > > Enis
> > >
> > > On Mon, Jan 11, 2016 at 11:05 AM, Sean Busbey <busbey@cloudera.com
> <javascript:;>
> > > <javascript:;>> wrote:
> > >
> > > > just to confirm, 'master' is no longer protected?
> > > >
> > > > On Mon, Jan 11, 2016 at 12:56 PM, Andrew Purtell <
> apurtell@apache.org <javascript:;>
> > > <javascript:;>>
> > > > wrote:
> > > >
> > > > > Infa recently announced on infrastructure@ that, following
> direction
> > > > from
> > > > > the Board, ASF git is now allowing force pushes and branch/tag
> > deletion
> > > > > again. In accordance with the guidance given by the Board there are
> > > some
> > > > > policy changes you should be aware of:
> > > > >
> > > > >    - First, if a forced commit is pushed, the subsequent commit
> email
> > > to
> > > > >    commits@ will contain '[Forced Update!]' in the subject line.
> The
> > > > hope
> > > > >    here is that it draws extra attention to the situation for a
> > project
> > > > >    community tobe aware, and take appropriate action if needed.
> > > > >
> > > > >    - Second, the 'protected' Git ref-space is now refs/tags/rel/*
.
> > Any
> > > > >    tags under rel/, can be assured to carry the complete immutable
> > > commit
> > > > >    history which lead up to the commit. This provides the
> provenance
> > > that
> > > > > the
> > > > >    ASF needs for releases. Otherwise projects can mold their
> > repository
> > > > ref
> > > > >    structure any way they see fit. When a release vote is
> successful
> > > part
> > > > > of
> > > > >    the release process should include tagging the voted upon commit
> > SHA
> > > > > under
> > > > >    rel/ to make it indelible. ('# git tag rel/v15.4.2 ' or
> something
> > > > > similar.)
> > > > >
> > > > > Let's incorporate the second point into our release process
> > > immediately.
> > > > We
> > > > > can also go back and add corresponding tags in refs/tags/rel/ for
> all
> > > of
> > > > > our past releases. Unless there are any objections I will take care
> > of
> > > > this
> > > > > housekeeping later this week.
> > > > >
> > > > > --
> > > > > Best regards,
> > > > >
> > > > >    - Andy
> > > > >
> > > > > Problems worthy of attack prove their worth by hitting back. - Piet
> > > Hein
> > > > > (via Tom White)
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sean
> > > >
> > >
> > >
> > >
> >
>
>
>
> --
> Sean
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message