[jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag jbosstools-4.3.0.Alpha2 ]

[Max Rydahl Andersen]

On 30 Apr 2015, at 22:54, Nick Boldt wrote:

> jbosstools-4.2.3.Final tag created for jbosstools-build (even though 
> we
> still have https://issues.jboss.org/browse/JBIDE-19744 open pending a 
> fix).

since that fix was not in when we did 4.2.3.Final then that is the 
correct state to tag.

> For these 2 projects below, branches don't exist for 4.3.0.Alpha2x so 
> I
> could not create tags. Will create branches for Beta1x and tag next 
> time.
>
> * jbosstools-build-ci

This one seem to be the important one since it has the jenkins jobs in 
use etc.

> * jbosstools-download.jboss.org

This one I wasn't sure about - might just make sense to do like we do 
for website.
tag when we push changes live ?

> Do you need me to compute which old SHAs map to old tags like
> 4.0.0.Final or 4.1.0.Beta1? Since those releases are done and we will
> only ever be building forward from 4.2.x (after 4.2.3.Final) and 4.3.x
> (after 4.3.0.Alpha2), do we need to go back into the past to create 
> old
> tags?

so I created a script that takes a csv file in this format:

orgname/reponame1, sha1
orgname/reponame2, sha1
...

and does tagging across all repo listed with name given as input.

Now, we have for years said we gathered what went into our builds (repos 
and their sha1's).

So here is the test for that  - can you provide me with those so we can 
generate that csv file
and we can fix the tags easily for missed pass commits ? (doesn't have 
to be today today, but just to
know how hard it would be to get this info we've said we collected per 
build)

...and we can setup this script for future
releases too.

/max
>
> Nick
>
> On 04/30/2015 07:21 AM, Max Rydahl Andersen wrote:
>>
>> Done for livereload and webservices - xcoulon is on PTO so I did it 
>> for him.
>>
>> posted here since getting these tags recorded are important.
>>
>> Things the tags are used for:
>> * build of jbosstools at fedora
>> * checking what went into a release when debugging
>> * knowing which components got into a relase
>>
>> Still missing:
>> jbosstools-portlet
>> jbosstools-freemarker
>> jbosstools-hibernate
>> jbosstools-aerogear
>> jbosstools-arquillian
>> jbosstools-download.jboss.org
>> jbosstools-build-ci
>> jbosstools-birt
>>
>> /max
>>
>>> Done for forge
>>>
>>> On 04/27/2015 07:22 PM, Nick Boldt wrote:
>>>> Component leads, please tag your repositories!
>>>>
>>>> git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
>>>> called jbosstools, also often called origin
>>>> git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
>>>> git push jbosstools jbosstools-4.3.0.Alpha2
>>>>
>>>>
>>>
>>> _______________________________________________
>>> 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
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen