llvm dev - May 2015 - [LLVMdev] 3.6.2 Release schedule + Using Phab for stable patches

Hi,

Here is the schedule for the 3.6.2 release:

June 15: Deadline to propose patches for the 3.6 branch
June 15 - June 21: Grace period for reviewing proposed patches and resolving
                   other issues.
June 22: 3.6.2 -rc1
June 29: 3.6.2 release

Also, I would like to try to try to experiment with using phabricator for
proposing patches to the stable branch.  This is not a requirement,
but it will help reduce the chances of your patch being missed.

I have created a 3.6-release project on phabricator, so if you would like
to propose a patch via phabricator you can create a new diff and select
'3.6-release' as the project.  Also make sure to include the ToT
revision number in the subject, something like:

Merge r237164 to 3.6 branch: R600/SI: Fix bug in VGPR spilling.

I'm also trying to figure out a way to create a submission
without a patch, because in most cases it is redundant to
specify a revision number and upload a patch.  If anyone has
any suggestions about this, please let me know.

Thanks,
Tom

+cfe-dev

On Wed, May 27, 2015 at 07:44:48AM -0700, Tom Stellard
wrote:
> Hi,
> 
> Here is the schedule for the 3.6.2 release:
> 
> June 15: Deadline to propose patches for the 3.6 branch
> June 15 - June 21: Grace period for reviewing proposed patches and
resolving
>                    other issues.
> June 22: 3.6.2 -rc1
> June 29: 3.6.2 release
> 
> Also, I would like to try to try to experiment with using phabricator for
> proposing patches to the stable branch.  This is not a requirement,
> but it will help reduce the chances of your patch being missed.
> 
> I have created a 3.6-release project on phabricator, so if you would like
> to propose a patch via phabricator you can create a new diff and select
> '3.6-release' as the project.  Also make sure to include the ToT
> revision number in the subject, something like:
> 
> Merge r237164 to 3.6 branch: R600/SI: Fix bug in VGPR spilling.
> 
> I'm also trying to figure out a way to create a submission
> without a patch, because in most cases it is redundant to
> specify a revision number and upload a patch.  If anyone has
> any suggestions about this, please let me know.
> 
> Thanks,
> Tom
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

> I'm also trying to figure out a way to create a submission
> without a patch, because in most cases it is redundant to
> specify a revision number and upload a patch.  If anyone has
> any suggestions about this, please let me know.
> 
> Thanks,
> Tom
It will need some Phabricator development but an extension to Audit (the
post-commit review tool at http://reviews.llvm.org/audit/) would make sense to
me. The idea is to nominate a revision for inclusion via the actions drop-down
in Audit and have that automatically create a Differential revision for the
branch (complete with the patch as it was committed to trunk). This would also
enable the review of conflict resolution for the occasions when it's
non-trivial.

Hi,

Just a reminder there is only one week left to nominate patches for the
3.6.2 release.  If you want to nominate a patch, the preferred method
is to upload the patch to reviews.llvm.org, put the ToT revsion number
in the 'Title' field, select 3.6-release as the project, and then
add me and the code owner as reviewers.

If you don't want to use phabricator, you can still send an email with the
proposed patch / ToT revision to the appropriate mailing list with
the code owner and myself cc'd

Thanks,
Tom

On Wed, May 27, 2015 at 08:00:47AM -0700, Tom Stellard
wrote:
> +cfe-dev
> 
> On Wed, May 27, 2015 at 07:44:48AM -0700, Tom Stellard wrote:
> > Hi,
> > 
> > Here is the schedule for the 3.6.2 release:
> > 
> > June 15: Deadline to propose patches for the 3.6 branch
> > June 15 - June 21: Grace period for reviewing proposed patches and
resolving
> >                    other issues.
> > June 22: 3.6.2 -rc1
> > June 29: 3.6.2 release
> > 
> > Also, I would like to try to try to experiment with using phabricator
for
> > proposing patches to the stable branch.  This is not a requirement,
> > but it will help reduce the chances of your patch being missed.
> > 
> > I have created a 3.6-release project on phabricator, so if you would
like
> > to propose a patch via phabricator you can create a new diff and
select
> > '3.6-release' as the project.  Also make sure to include the
ToT
> > revision number in the subject, something like:
> > 
> > Merge r237164 to 3.6 branch: R600/SI: Fix bug in VGPR spilling.
> > 
> > I'm also trying to figure out a way to create a submission
> > without a patch, because in most cases it is redundant to
> > specify a revision number and upload a patch.  If anyone has
> > any suggestions about this, please let me know.
> > 
> > Thanks,
> > Tom
> > _______________________________________________
> > LLVM Developers mailing list
> > LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev