[Hawkular-dev] Pushing 'hawkular-1275' branches to master (Done)

[Jay Shaughnessy]

Note that the master branches now contain the Prometheus-based 
components for:

   hawkular-commons
   hawkular-agent
   hawkular-services

The hawkular-1275 branches are no longer in use.  The proper Services 
docker container label is now 'latest'.


On 12/15/2017 10:55 AM, Jay Shaughnessy wrote:
>
> At this point please refrain from generating PRs against the 
> hawkular-1275 branches.  We are in the process of migrating to 
> master.  The Hawkular Commons PR is generated, after it is merged we 
> can merge Hawkular Agent, and then Hawkular Services.  It should be 
> completed no later than Monday.
>
> On 12/14/2017 9:18 AM, Jay Shaughnessy wrote:
>>
>> Note that this is for the server-side repos:
>>   hawkular-commons
>>   hawkular-agent
>>   hawkular-services
>>
>> The provider side repos (ruby/miq) will remain in the hawkular-1328 
>> branches hosted by Edgar's github account.
>>
>> On 12/13/2017 2:06 PM, Matthew Wringe wrote:
>>> Unless there is any objection, we would like to merge the 
>>> hawkular-1275 branches to master and continue to work in the master 
>>> branch.
>>>
>>> Once we are in the master branch we will also be moving towards a 
>>> one PR per jira issue. The workflow in jira will require this and 
>>> will automatically close the jira when a PR is merged.
>>>
>>> Thanks,
>>>
>>> Matt Wringe
>>>
>>>
>>> _______________________________________________
>>> hawkular-dev mailing list
>>> hawkular-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171219/b399f77b/attachment.html