Re: ReSpec updated

We are painfully aware that we screwed up a bunch of people.  You have no
idea how aware.

I am going to put new processes in place moving forward.  As to rolling
back to stable versions.... yes, we should have done that two weeks ago.  I
considered it several times.  I could have pulled a branch off and created
a new release with the 1 change needed.  I got wrapped up in the "we are 2
seconds from fixing the core problem" mindset.  For 10 days. I am very
upset with myself.  You would think after 35 years in the industry I would
know better.

On Thu, Mar 10, 2016 at 1:49 PM, Tobie Langel <tobie@codespeaks.com> wrote:

> On Thu, 10 Mar 2016, at 20:38, Michael Cooper wrote:
>
> I'm sorry, I don't mean to sound entitled, but recognize that the wording
> of my message does sound that way. I know Respec is a volunteer project
> made available for free. I would like to be able to contribute and share
> the load, but it uses a technology I just don't have skills in. So I have
> to depend on the people who do maintain it, to do so carefully. I think
> this whole recent episode shows the need to be careful with a production
> version, and to engage more people in review of development versions.
> Though I can't produce useful pull requests, I could provide useful input
> on something that I'm not depending on urgently for publication, but
> haven't known how to engage with that process. Michael
>
>
> Apologies accepted. :)
>
> I do think the team is quite aware that this update happened in less than
> ideal conditions (though again, I can't speak on their behalf).
>
> It might be worth discussing solutions to easily switch to a previous
> stable version in case the latest release has bugs which block you from
> publishing (I think Shane kind of informally set something of that sort up
> recently).
>
> --tobie
>
>
>
>



-- 
Shane McCarron
Projects Manager, Spec-Ops