<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/2.x/2026-01-27-12-two-branch-strategy-for-saas-transformation/">
  <id>https://docs.spec-kitty.ai/adr/2.x/2026-01-27-12-two-branch-strategy-for-saas-transformation/</id>
  <title>Two-Branch Strategy for SaaS Transformation</title>
  <updated>2026-01-27T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/2.x/2026-01-27-12-two-branch-strategy-for-saas-transformation/"/>
  <summary>Ships stable local-only 1.x while 2.x develops event sourcing and sync on greenfield, deferring the state migration until the distributed design proves itself.</summary>
  <content type="html">&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;Spec-kitty 1.x is nearing production readiness as a local-only CLI tool. Meanwhile, the SaaS transformation (Features 001-004+) requires fundamental changes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Event sourcing with Lamport clocks (replacing YAML activity logs)&lt;/li&gt;
&lt;li&gt;Distributed state management with CRDT merge rules&lt;/li&gt;
&lt;li&gt;Sync protocol for CLI ↔ Django communication&lt;/li&gt;
&lt;li&gt;Private dependency on spec-kitty-events library&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Constraints:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Users are actively using 1.x features (cannot break existing workflows)&lt;/li&gt;
&lt;li&gt;SaaS features will take months to complete (Event Log → Sync Protocol → Connector Hub)&lt;/li&gt;
&lt;li&gt;Progressive migration would require maintaining dual state systems (YAML + events)&lt;/li&gt;
&lt;li&gt;No team resources for parallel 1.x feature development during 2.x transformation&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Question:&lt;/strong&gt; How do we ship a stable 1.x release while building the SaaS-enabled 2.x without breaking current users or accumulating migration debt?&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;User stability&lt;/strong&gt; - 1.x users need a stable, supported version without forced upgrades&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Development velocity&lt;/strong&gt; - 2.x needs greenfield freedom without 1.x compatibility constraints&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Migration complexity&lt;/strong&gt; - Deferred migration is simpler than progressive migration&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Resource constraints&lt;/strong&gt; - Solo developer cannot maintain two active feature branches&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Release pressure&lt;/strong&gt; - Need to ship 1.x soon, but 2.x will take months to complete&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dependency management&lt;/strong&gt; - 2.x has private dependencies (spec-kitty-events) that 1.x doesn’t need&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;considered-options&quot;&gt;Considered Options&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Option 1:&lt;/strong&gt; Two-branch strategy with deferred migration&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Option 2:&lt;/strong&gt; Progressive migration (dual state systems in single branch)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Option 3:&lt;/strong&gt; Postpone 1.x release until 2.x is complete&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Option 4:&lt;/strong&gt; Feature flags for SaaS features (gradual rollout)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision-outcome&quot;&gt;Decision Outcome&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Chosen option:&lt;/strong&gt; “Two-branch strategy with deferred migration”, because it:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Allows shipping stable 1.x immediately without SaaS complexity&lt;/li&gt;
&lt;li&gt;Gives 2.x greenfield development freedom (no backward compatibility burden)&lt;/li&gt;
&lt;li&gt;Defers migration complexity until 2.x is substantially complete and proven&lt;/li&gt;
&lt;li&gt;Avoids maintaining dual state systems during transition period&lt;/li&gt;
&lt;li&gt;Cleanly separates concerns (local-only vs. distributed architecture)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;consequences&quot;&gt;Consequences&lt;/h3&gt;
&lt;h4 id=&quot;positive&quot;&gt;Positive&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Stable 1.x release&lt;/strong&gt; - Ship production-ready local-only tool without SaaS dependencies&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Greenfield 2.x&lt;/strong&gt; - No backward compatibility constraints during fundamental architecture changes&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deferred migration&lt;/strong&gt; - Build migration tools when 2.x is proven and stable&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clear user expectations&lt;/strong&gt; - 1.x users know they’re on maintenance-only track&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No dual state systems&lt;/strong&gt; - Avoid complexity of maintaining YAML + events simultaneously&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Resource focus&lt;/strong&gt; - Solo developer concentrates fully on 2.x without 1.x feature requests&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;negative&quot;&gt;Negative&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Branch divergence&lt;/strong&gt; - 1.x and 2.x will accumulate differences (harder to cherry-pick fixes)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Duplicate bug fixes&lt;/strong&gt; - Critical bugs may need fixing in both branches during transition&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;User fragmentation&lt;/strong&gt; - Some users stay on 1.x, others adopt 2.x (split community)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Migration effort&lt;/strong&gt; - Must build migration tools later (deferred cost, not avoided)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Documentation split&lt;/strong&gt; - Need separate docs for 1.x and 2.x&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;neutral&quot;&gt;Neutral&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;1.x maintenance&lt;/strong&gt; - Security/critical fixes only, no new features&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No forced migration&lt;/strong&gt; - Users can stay on 1.x indefinitely if they don’t need SaaS&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;2.x release timeline&lt;/strong&gt; - Months away (Event Log → Sync Protocol → Connector Hub → Beta)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;confirmation&quot;&gt;Confirmation&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Validation signals:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;1.x release ships cleanly without SaaS infrastructure (validation: no spec-kitty-events dependency)&lt;/li&gt;
&lt;li&gt;2.x development proceeds without 1.x compatibility PRs (validation: no “support both” code)&lt;/li&gt;
&lt;li&gt;Migration tools work when 2.x nears completion (validation: automated migration script succeeds)&lt;/li&gt;
&lt;li&gt;Users understand branch strategy (validation: clear documentation, no confusion issues)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Confidence level:&lt;/strong&gt; High - This is a standard strategy for major version transitions (Python 2→3, Angular 1→2, etc.)&lt;/p&gt;
&lt;h2 id=&quot;pros-and-cons-of-the-options&quot;&gt;Pros and Cons of the Options&lt;/h2&gt;
&lt;h3 id=&quot;option-1-two-branch-strategy-with-deferred-migration&quot;&gt;Option 1: Two-Branch Strategy with Deferred Migration&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;1.x Branch:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Local-only CLI tool&lt;/li&gt;
&lt;li&gt;YAML activity logs (existing system)&lt;/li&gt;
&lt;li&gt;No event sourcing, no sync protocol&lt;/li&gt;
&lt;li&gt;Maintenance-only after initial release (security + critical bugs)&lt;/li&gt;
&lt;li&gt;PyPI releases continue (1.0.0, 1.0.1, 1.0.2, etc.)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;2.x Branch:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Greenfield SaaS transformation&lt;/li&gt;
&lt;li&gt;Event sourcing with spec-kitty-events library&lt;/li&gt;
&lt;li&gt;Sync protocol for CLI ↔ Django&lt;/li&gt;
&lt;li&gt;No backward compatibility with 1.x state&lt;/li&gt;
&lt;li&gt;No PyPI releases until substantially complete&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Migration Strategy:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Deferred until 2.x nears beta/stable&lt;/li&gt;
&lt;li&gt;Migration tool: &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate-to-2x&lt;/code&gt; command (to be built later)&lt;/li&gt;
&lt;li&gt;Converts 1.x YAML logs → 2.x event log&lt;/li&gt;
&lt;li&gt;User-initiated (not automatic)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Clean separation of concerns (local vs. distributed)&lt;/li&gt;
&lt;li&gt;Greenfield freedom for 2.x (no compatibility constraints)&lt;/li&gt;
&lt;li&gt;Stable 1.x immediately available&lt;/li&gt;
&lt;li&gt;Simpler than dual state systems&lt;/li&gt;
&lt;li&gt;Clear user expectations (maintenance vs. active development)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Branch divergence accumulates over time&lt;/li&gt;
&lt;li&gt;Bug fixes may need applying to both branches&lt;/li&gt;
&lt;li&gt;Migration effort deferred (cost paid later)&lt;/li&gt;
&lt;li&gt;Community fragmentation during transition&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;option-2-progressive-migration-dual-state-systems&quot;&gt;Option 2: Progressive Migration (Dual State Systems)&lt;/h3&gt;
&lt;p&gt;Single &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; branch with both YAML and event log systems active. Feature flags control which system is used.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;No branch divergence&lt;/li&gt;
&lt;li&gt;Users can opt-in to event log incrementally&lt;/li&gt;
&lt;li&gt;Single codebase to maintain&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;❌ &lt;strong&gt;Complexity explosion&lt;/strong&gt; - Maintaining two state systems simultaneously (YAML + events)&lt;/li&gt;
&lt;li&gt;❌ &lt;strong&gt;Testing burden&lt;/strong&gt; - Must test all combinations (YAML-only, events-only, hybrid)&lt;/li&gt;
&lt;li&gt;❌ &lt;strong&gt;Performance overhead&lt;/strong&gt; - Dual writes to both systems during transition&lt;/li&gt;
&lt;li&gt;❌ &lt;strong&gt;Migration never completes&lt;/strong&gt; - Technical debt accumulates (when can we remove YAML?)&lt;/li&gt;
&lt;li&gt;❌ &lt;strong&gt;Confusing for users&lt;/strong&gt; - Unclear which mode they’re in, hybrid state bugs&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;option-3-postpone-1x-release-until-2x-complete&quot;&gt;Option 3: Postpone 1.x Release Until 2.x Complete&lt;/h3&gt;
&lt;p&gt;Delay 1.x release until SaaS features are complete, ship only 2.x.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;No branch management complexity&lt;/li&gt;
&lt;li&gt;Users get best-in-class SaaS experience immediately&lt;/li&gt;
&lt;li&gt;No migration needed (never shipped 1.x)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;❌ &lt;strong&gt;Delays stable release by months&lt;/strong&gt; - Users waiting for production-ready tool&lt;/li&gt;
&lt;li&gt;❌ &lt;strong&gt;Higher risk&lt;/strong&gt; - First release includes complex SaaS features (more bugs)&lt;/li&gt;
&lt;li&gt;❌ &lt;strong&gt;Lost feedback&lt;/strong&gt; - Cannot learn from 1.x users before building SaaS&lt;/li&gt;
&lt;li&gt;❌ &lt;strong&gt;All-or-nothing&lt;/strong&gt; - Forces SaaS on users who only need local tool&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;option-4-feature-flags-for-saas-features&quot;&gt;Option 4: Feature Flags for SaaS Features&lt;/h3&gt;
&lt;p&gt;Single branch with feature flags: &lt;code dir=&quot;auto&quot;&gt;--enable-events&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--enable-sync&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Gradual rollout possible&lt;/li&gt;
&lt;li&gt;Users control adoption pace&lt;/li&gt;
&lt;li&gt;Single codebase&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;❌ &lt;strong&gt;Combinatorial explosion&lt;/strong&gt; - Testing matrix: events ON/OFF × sync ON/OFF × …&lt;/li&gt;
&lt;li&gt;❌ &lt;strong&gt;Default dilemma&lt;/strong&gt; - What should be default? (Forces decision prematurely)&lt;/li&gt;
&lt;li&gt;❌ &lt;strong&gt;Incomplete features&lt;/strong&gt; - Half-working SaaS features confuse users&lt;/li&gt;
&lt;li&gt;❌ &lt;strong&gt;Technical debt&lt;/strong&gt; - When can flags be removed? (Never clear)&lt;/li&gt;
&lt;li&gt;❌ &lt;strong&gt;Still requires dual state&lt;/strong&gt; - Same complexity as Option 2&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;more-information&quot;&gt;More Information&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Implementation Details:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Branch Naming Decision:&lt;/strong&gt; After analysis, we chose to create &lt;strong&gt;separate &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt; branch&lt;/strong&gt; (not reuse main):&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;main Branch (becomes 1.x):&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Current: v0.13.x (stable development)&lt;/li&gt;
&lt;li&gt;Future: v1.x (maintenance-only after v1.0.0 release)&lt;/li&gt;
&lt;li&gt;No formal “1.x branch” created (main IS the 1.x line)&lt;/li&gt;
&lt;li&gt;Branch protection: Only security/critical fixes merged after v1.0.0&lt;/li&gt;
&lt;li&gt;No new features (frozen feature set)&lt;/li&gt;
&lt;li&gt;YAML activity logs (existing system)&lt;/li&gt;
&lt;li&gt;Documentation: “Spec Kitty 1.x (Local Mode)”&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;2.x Branch (created 2026-01-27):&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Branch: &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt; (NEW branch created from main)&lt;/li&gt;
&lt;li&gt;Created from: main at v0.13.7 (commit c11ae57)&lt;/li&gt;
&lt;li&gt;Active development: Features 025+ (Event Log → Sync Protocol → SaaS)&lt;/li&gt;
&lt;li&gt;Private dependency: spec-kitty-events via Git (ADR-11)&lt;/li&gt;
&lt;li&gt;Greenfield architecture (incompatible with 1.x)&lt;/li&gt;
&lt;li&gt;No PyPI releases until substantially complete&lt;/li&gt;
&lt;li&gt;Documentation: “Spec Kitty 2.x (SaaS Mode) - Beta”&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Rationale for separate branch&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Avoids confusion (main clearly remains stable)&lt;/li&gt;
&lt;li&gt;Enables parallel PRs (1.x fixes on main, 2.x features on 2.x)&lt;/li&gt;
&lt;li&gt;Clearer git history (2.x commits don’t pollute main)&lt;/li&gt;
&lt;li&gt;Option to rebase 2.x periodically from main (cherry-pick critical fixes)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Migration Plan (Deferred to Future Feature):&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Feature: “2.x Migration Tool” (build when 2.x nears beta)&lt;/li&gt;
&lt;li&gt;Command: &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate-to-2x&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Behavior:
&lt;ol&gt;
&lt;li&gt;Detect 1.x project (&lt;code dir=&quot;auto&quot;&gt;.kittify/activity.yaml&lt;/code&gt; exists)&lt;/li&gt;
&lt;li&gt;Parse YAML activity logs&lt;/li&gt;
&lt;li&gt;Convert to event log with synthetic Lamport clocks (ordered by timestamp)&lt;/li&gt;
&lt;li&gt;Write to &lt;code dir=&quot;auto&quot;&gt;.kittify/events/YYYY-MM-DD.jsonl&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Mark project as 2.x (version flag in config)&lt;/li&gt;
&lt;li&gt;Archive 1.x state to &lt;code dir=&quot;auto&quot;&gt;.kittify/1x-backup/&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Communication Strategy:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;README badge: “Spec Kitty 1.x (Maintenance Mode)” vs. “Spec Kitty 2.x (Active Development)”&lt;/li&gt;
&lt;li&gt;CHANGELOG: Clear separation of 1.x and 2.x changes&lt;/li&gt;
&lt;li&gt;Documentation: Separate sections for 1.x and 2.x&lt;/li&gt;
&lt;li&gt;GitHub Issues: Tags &lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt; for triage&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Related Decisions:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ADR-11: Dual-Repository Pattern (spec-kitty-events dependency)&lt;/li&gt;
&lt;li&gt;Feature 001: SaaS Transformation Research (roadmap)&lt;/li&gt;
&lt;li&gt;Feature 002: Event Log Storage Research (LWW flaw discovery)&lt;/li&gt;
&lt;li&gt;Feature 003: Event Log Library (spec-kitty-events implementation)&lt;/li&gt;
&lt;li&gt;Feature 004: CLI Event Log Integration (2.x foundation)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Future Considerations:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;If 2.x adoption is slow, consider maintaining 1.x longer&lt;/li&gt;
&lt;li&gt;If critical 1.x bugs are frequent, reconsider maintenance-only policy&lt;/li&gt;
&lt;li&gt;If migration proves too complex, may need hybrid transition period (dual state)&lt;/li&gt;
&lt;li&gt;Community feedback will determine 1.x end-of-life timeline&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Code References:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;1.x line&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;git checkout main&lt;/code&gt; (current: v0.13.x, future: v1.x after v1.0.0 release)
&lt;ul&gt;
&lt;li&gt;No separate “1.x branch” created (main IS the 1.x line)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;2.x branch&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;git checkout 2.x&lt;/code&gt; (created 2026-01-27 from main at c11ae57)
&lt;ul&gt;
&lt;li&gt;Branch created: &lt;code dir=&quot;auto&quot;&gt;git checkout -b 2.x &amp;#x26;&amp;#x26; git push origin 2.x&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Migration script&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/migrate_to_2x.py&lt;/code&gt; (to be created later)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;How to contribute&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;For stable 1.x fixes&lt;/strong&gt;: Branch from main, PR to main&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;For 2.x SaaS features&lt;/strong&gt;: Branch from 2.x, PR to 2.x&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;See branches&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;git branch -a | grep -E &quot;(main|2.x)&quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
