ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag jbosstools-4.3.0.Alpha2 ]
12:22 a.m.
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
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
11:53 a.m.
done for OpenShift
On 04/28/2015 12:22 AM, 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
3:41 p.m.
Just FYI, you don't need to reply to these emails to confirm the work's
done.
Thanks,
Nick
On 04/28/2015 05:53 AM, André Dietisheim wrote:
done for OpenShift
On 04/28/2015 12:22 AM, 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
>
>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
4:08 p.m.
too late :)
On 04/28/2015 10:41 AM, Nick Boldt wrote:
Just FYI, you don't need to reply to these emails to confirm the
work's
done.
Thanks,
Nick
On 04/28/2015 05:53 AM, André Dietisheim wrote:
> done for OpenShift
>
> On 04/28/2015 12:22 AM, 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
>>
>>
8:01 p.m.
On 28 Apr 2015, at 15:41, Nick Boldt wrote:
Just FYI, you don't need to reply to these emails to confirm the
work's
done.
Nick, do you have a script that checks if all done ?
/max
Thanks,
Nick
On 04/28/2015 05:53 AM, André Dietisheim wrote:
> done for OpenShift
>
> On 04/28/2015 12:22 AM, 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
>>
>>
>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
10:55 p.m.
No, but I have a script that checks if everyone has branched & if root
poms are updated, because...
* Wrong root pom: prevents builds & blocks releases.
* Branching: prevents builds & blocks releases.
* Tagging: until we move to a model where tags drive builds, tagging
after the release is just icing sugar.
You may now commence arguing. :D
Nick
On 04/28/2015 02:01 PM, Max Rydahl Andersen wrote:
On 28 Apr 2015, at 15:41, Nick Boldt wrote:
> Just FYI, you don't need to reply to these emails to confirm the work's
> done.
Nick, do you have a script that checks if all done ?
/max
> Thanks,
>
> Nick
>
> On 04/28/2015 05:53 AM, André Dietisheim wrote:
>> done for OpenShift
>>
>> On 04/28/2015 12:22 AM, 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
>>>
>>>
>>
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
12:35 a.m.
I'll write the script. Having the tags has been and will be useful in past despite you
thinking it is just icing.
/max
http://about.me/maxandersen
On 28 Apr 2015, at 22:55, Nick Boldt <nboldt(a)redhat.com>
wrote:
No, but I have a script that checks if everyone has branched & if root poms are
updated, because...
* Wrong root pom: prevents builds & blocks releases.
* Branching: prevents builds & blocks releases.
* Tagging: until we move to a model where tags drive builds, tagging after the release is
just icing sugar.
You may now commence arguing. :D
Nick
> On 04/28/2015 02:01 PM, Max Rydahl Andersen wrote:
>> On 28 Apr 2015, at 15:41, Nick Boldt wrote:
>>
>> Just FYI, you don't need to reply to these emails to confirm the work's
>> done.
>
> Nick, do you have a script that checks if all done ?
>
> /max
>
>> Thanks,
>>
>> Nick
>>
>>> On 04/28/2015 05:53 AM, André Dietisheim wrote:
>>> done for OpenShift
>>>
>>>> On 04/28/2015 12:22 AM, 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
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
4:08 p.m.
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
1:21 p.m.
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
10:30 p.m.
Done for freemarker.
Should we run tagging verification script after release is declared and it
would keep pinging component leads until tag is created?
On Thu, Apr 30, 2015 at 4:21 AM, Max Rydahl Andersen <manderse(a)redhat.com>
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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
1:12 a.m.
On 30 Apr 2015, at 22:30, Denis Golovin wrote:
Done for freemarker.
thanks!
script still finds these missing though.
jbosstools-freemarker missing 11 tags:
jbosstools-4.1.0.Beta1,
jbosstools-4.1.1.Beta1,
jbosstools-4.1.1.CR1,
jbosstools-4.1.1.Final,
jbosstools-4.1.2.Final,
jbosstools-4.2.0.Alpha1,
jbosstools-4.2.0.Beta1,
jbosstools-4.2.0.Beta2,
jbosstools-4.2.3.Beta1,
jbosstools-4.2.3.CR1,
jbosstools-4.3.0.Alpha1
so I assume you just did it for alpha2, right ?
Should we run tagging verification script after release is declared
and it
would keep pinging component leads until tag is created?
yeah - but I think I got a script now that can do this via github api
meaning I need no
git clones etc. just the list of repos and sha1's that our builds should
have.
see other mail.
/max
On Thu, Apr 30, 2015 at 4:21 AM, Max Rydahl Andersen
<manderse(a)redhat.com>
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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
/max
http://about.me/maxandersen
1:19 a.m.
On Thu, Apr 30, 2015 at 4:12 PM, Max Rydahl Andersen <manderse(a)redhat.com>
wrote:
On 30 Apr 2015, at 22:30, Denis Golovin wrote:
Done for freemarker.
>
thanks!
script still finds these missing though.
jbosstools-freemarker missing 11 tags:
jbosstools-4.1.0.Beta1,
jbosstools-4.1.1.Beta1,
jbosstools-4.1.1.CR1,
jbosstools-4.1.1.Final,
jbosstools-4.1.2.Final,
jbosstools-4.2.0.Alpha1,
jbosstools-4.2.0.Beta1,
jbosstools-4.2.0.Beta2,
jbosstools-4.2.3.Beta1,
jbosstools-4.2.3.CR1,
jbosstools-4.3.0.Alpha1
so I assume you just did it for alpha2, right ?
Yeah, alpha2 only.
Should we run tagging verification script after release is declared and it
> would keep pinging component leads until tag is created?
>
yeah - but I think I got a script now that can do this via github api
meaning I need no
git clones etc. just the list of repos and sha1's that our builds should
have.
see other mail.
/max
> On Thu, Apr 30, 2015 at 4:21 AM, Max Rydahl Andersen <manderse(a)redhat.com
> >
> 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(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>
>>
>> /max
>> http://about.me/maxandersen
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
/max
http://about.me/maxandersen
10:54 p.m.
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).
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
* jbosstools-download.jboss.org
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?
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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)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
1:17 a.m.
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.
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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
3284
days inactive
3287
days old
jbosstools-dev@lists.jboss.org
13 comments
5 participants
participants (5)
-
André Dietisheim -
Denis Golovin -
George Gastaldi -
Max Rydahl Andersen -
Nick Boldt