<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Setup-task #4 &#8211; CS@Worcester</title>
	<atom:link href="https://cs.worcester.edu/category/setup-task-4/feed/" rel="self" type="application/rss+xml" />
	<link>https://cs.worcester.edu</link>
	<description>Worcester State University Computer Science Department</description>
	<lastBuildDate>Mon, 24 Jan 2022 01:02:45 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
<site xmlns="com-wordpress:feed-additions:1">236835116</site>	<item>
		<title>CS 448-02 –   Setup Task # 4                        Conventional Commits </title>
		<link>https://twinstarjoecom.wordpress.com/2022/01/23/post-2-conventional-commits/</link>
		
		<dc:creator><![CDATA[Joe Barry]]></dc:creator>
		<pubDate>Mon, 24 Jan 2022 01:02:45 +0000</pubDate>
				<category><![CDATA[CS-448]]></category>
		<category><![CDATA[CS@Worcester]]></category>
		<category><![CDATA[Setup-task #4]]></category>
		<guid isPermaLink="false">http://twinstarjoecom.wordpress.com/?p=139</guid>

					<description><![CDATA[I found the conventional commits description under “Thea’s Pantry Workflow” interesting. This is new to me, but I see the importance of being able to control all developers to use the same formula in describing commits. It is also necessary to use the semantic versioning [1] to not only be an asset to developers and…<span class="excerpt-more-link"><a class="more-link" href="https://twinstarjoecom.wordpress.com/2022/01/23/post-2-conventional-commits/">More </a></span>]]></description>
										<content:encoded><![CDATA[<p>I found the conventional commits description under “Thea’s Pantry Workflow” interesting. This is new to me, but I see the importance of being able to control all developers to use the same formula in describing commits. It is also necessary to use the semantic versioning <strong>[1]</strong> to not only be an asset to developers and managers following other developer’s work in a controlled manner, but allowing the connection of the GitLab commits to be integrated with testing, and deployment in an automated fashion (CI/CD)</p>
<p><strong>[1] &nbsp;FIX/PATCH</strong>&nbsp; &#8211; generally bug fixes</p>
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <strong>FEAT/MINOR</strong> – a full new feature that does not break the code-base,</p>
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <strong>BREAKING CHANGE/MAJOR</strong>.</p>
<p> I am also interested in learning Kubernetes, as well as understanding better how continuous integration and deployment will be used in our product.</p>

<p class="syndicated-attribution"><em>From the blog <a href="https://twinstarjoecom.wordpress.com">cs@worcester – (Twinstar Blogland) </a> by <a href="https://cs.worcester.edu/author/0/" title="Read other posts by Joe Barry">Joe Barry</a></em> and used with permission of the author. All other rights reserved by the author.</p>]]></content:encoded>
					
		
		<enclosure url="https://1.gravatar.com/avatar/1026e2e74bdf0720a3d1c33706178aec?s=96&#038;d=identicon&#038;r=G" length="0" type="" />

		<post-id xmlns="com-wordpress:feed-additions:1">16424</post-id>	</item>
	</channel>
</rss>
