I think it would be better to at least move the code to a 6.0 branch on the
main repository, just so that the code is a little easier to find for
external contributors/users. Even if it's named "6.0-wip" to mention that
you may end up rewriting history on that branch. If we release binaries,
then t
On Mon, 26 Nov 2018, 23:39 Gail Badner That's fine with me.
>
+1 But could you push the release tag to the reference repo? Just to make
sure we have it for future reference.
Thanks
> On Mon, Nov 26, 2018 at 11:29 AM Steve Ebersole
> wrote:
>
> > This Wednesday we plan to release 6.0 Alpha1 an
That's fine with me.
On Mon, Nov 26, 2018 at 11:29 AM Steve Ebersole wrote:
> This Wednesday we plan to release 6.0 Alpha1 and I thought it best to start
> discussing how to best handle the 6.0 and master branches.
>
> I think we should keep 6.0 a little while longer in my fork and 5.4 as
> mast
This Wednesday we plan to release 6.0 Alpha1 and I thought it best to start
discussing how to best handle the 6.0 and master branches.
I think we should keep 6.0 a little while longer in my fork and 5.4 as
master until 6.0 becomes more stabilized to make it easier for 5.4
maintenance. And reconsi
