[jbosstools-dev] ATTENTION REQUIRED: missing tags

[Nick Boldt]

Whoah, now. Tagging the tip of the 4.2.x branch and calling it something 
like 4.2.1.Final is a bad, and inaccurate plan.

If you need to dig up the SHAs for a given historical build, they can be 
found here:

http://download.jboss.org/jbosstools/builds/stable

For example, the SHAs that went into JBT 4.2.1.Final are here:

http://download.jboss.org/jbosstools/builds/stable/jbosstools-4.2.1.Final-build-core/2014-12-14_19-43-15-B320/logs/ALL_REVISIONS.txt

As to the actual steps for tagging from a SHA... I'm no gitsplainer, but 
I believe this is all you need to do:

    git tag <tagname> <SHA-of-the-commit>

If that's incorrect, I'm sure Max will correct me.

Nick

On 05/01/2015 09:23 PM, Max Rydahl Andersen wrote:
> On 1 May 2015, at 23:33, Rob Stryker wrote:
>
>> Maybe I'm missing something, but, how do we go and accurately tag
>> previous releases? Do we have the old SHA tags stored somewhere for
>> old builds?  Otherwise I don't see how its possible to go and
>> accurately tag our previous releases.
>
> That is what I asked Nick about since we have been supposed to gather
> that for all builds. Waiting for the answer.
>
> But if not there, then you can start by tagging the tip of the branch
> they should have been made on.
>
> /max
>
>
>>
>> On 05/01/2015 05:11 PM, Max Rydahl Andersen wrote:
>>> If you want the 100% method we need to build from the tag, meaning
>>> Dev need start doing their tags and declare them into the build.
>>>
>>> But can we tackle one issue at the time, please :)
>>>
>>> I would like to at least have our past final releases tagged
>>> consistently.
>>>
>>> We got it for most - just a few stands out.
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>>>
>>>> On 01 May 2015, at 16:51, Rob Stryker <rstryker at redhat.com> wrote:
>>>>
>>>>> On 04/29/2015 01:54 PM, Max Rydahl Andersen wrote:
>>>>> I would prefer it actually tagged the sha1 that was used instead of
>>>>> just assumed used.
>>>> Are we any closer to this happening?  What's still 'missing' to make
>>>> this a possibility?
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com