<div dir="ltr">I think the cli project is going to go unmaintained, and would be a big cost in dev-time otherwise.<div>I've only ever used it to clone the repos initially, and get started through its arbitrary npm linking, but since we have to constantly switch between checking out branches locally and installing pre-release versions to sanity-check them, it becomes very painful to manage these.</div><div><br></div><div>pros would be:<br></div><div>- reducing the number of different repos: perhaps down to 1 or keeping the demo apps as separate modules, not sure</div><div>- consolidating releases across the different sub-modules: currently we have separate versions for each module, and bumps involve a lot of manual updating of the trees and some shrinkwrapping,</div><div>with one repo we can use the same version for all sub-modules like babel does, makes it simpler for customers and platform templates as well</div><div>- single feature branches: we've had a couple of epics that had 5+ feature branches with the same name, the workflow and final merging got complicated!</div><div>- better supported than -cli: I haven't thought of lerna as an alternative to the cli because it would affect the repo structure itself, but it's a 3.2k star project used by a lot of high-profile projects itself.</div><div>It is potentially another tool as Emilio pointed out, but better chances we get contributors that are familiar with (or willing to learn) that tool than our own reinvented wheel, isn't that what OSS is all about? ;)</div><div><br></div><div>I thought this would be a nice fit stemming from Peter's comment in the Renaming Raincatcher packages thread, of course the forking-based model is still a bummer.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 9, 2017 at 7:51 AM, paul wright <span dir="ltr"><<a href="mailto:pwright@redhat.com" target="_blank">pwright@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Hi,</p>
<p>I didn't know about raincatcher-cli, thanks @Wojciech</p>
<p>From a docs POV, I'd like to move the end user info in the readme
to
<a class="m_6093741392744246570moz-txt-link-freetext" href="https://github.com/feedhenry-raincatcher/raincatcher-documentation" target="_blank">https://github.com/feedhenry-<wbr>raincatcher/raincatcher-<wbr>documentation</a>
(asciidoc rather than markdown, book structure rather than
readme).</p>
<p>What would remain in the readme is any info about contributing to
the project that you want to write, and a link to the docs repo.</p>
<p>Make sense?</p>
<p>thanks,</p>
<p>Paul<br>
</p><div><div class="h5">
<br>
<div class="m_6093741392744246570moz-cite-prefix">On 09/02/17 09:34, Wojciech Trocki
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Just to make it clear.
<div><br>
<div>Would you guys see this as replacement of <a href="https://github.com/feedhenry-raincatcher/raincatcher-cli" target="_blank">https://github.com/<wbr>feedhenry-raincatcher/<wbr>raincatcher-cli</a>
or something that is integrated into cli?<br>
Raincatcher-cli offers somehow similar functionalities at
the moment.</div>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="m_6093741392744246570gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div style="font-size:12.8px"><span style="color:rgb(153,153,153);font-size:small">Wojciech
Trocki</span></div>
<div>
<div><font color="#999999" size="2">Software
Engineer</font><font style="font-size:small" color="#999999">, </font><span style="font-size:small;color:rgb(153,153,153)">Red
Hat Mobile</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Thu, Feb 9, 2017 at 9:26 AM, Emilio
Rodriguez Martinez <span dir="ltr"><<a href="mailto:emrodrig@redhat.com" target="_blank">emrodrig@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I worked with Lerna in the past and I have to
say it's a great tool so I'm all in for it. Only downside
I see is we would be adding another tool for the users to
learn when working on the project.
<div><br>
</div>
<div>In any case, yeah, I think this is a much better
approach than the named branches.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div class="m_6093741392744246570h5">On Thu, Feb 9, 2017 at 1:58 AM, Paolo
Haji <span dir="ltr"><<a href="mailto:phaji@redhat.com" target="_blank">phaji@redhat.com</a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div class="m_6093741392744246570h5">
<div dir="ltr">Hey guys,
<div><br>
</div>
<div>This seems to be a great tool to deal with
the huge amount of small repos we want to keep
with raincatcher: <a href="https://lernajs.io/" target="_blank">https://lernajs.i<wbr>o/</a></div>
<div><br>
</div>
<div>Looks like it's used by a lot of
high-profile projects with needs similar to
ours. Beats creating a bunch of feature
branches with the same name.</div>
<div><br>
</div>
<div>As a plus <a href="https://github.com/lerna/lerna-changelog" target="_blank">lerna-changelog</a> generates
nice changelogs based on PR tags to categorize
changes. <a href="https://github.com/babel/babel/blob/master/lerna.json#L10" target="_blank">babel's</a> <a href="https://github.com/babel/babel/blob/master/CHANGELOG.md#bug-bug-fix" target="_blank">example</a> uses emoji in
their convention, which might appeal specially
to Ger (cc'd)</div>
</div>
<br>
</div>
</div>
______________________________<wbr>_________________<br>
Feedhenry-raincatcher mailing list<br>
<a href="mailto:Feedhenry-raincatcher@redhat.com" target="_blank">Feedhenry-raincatcher@redhat.c<wbr>om</a><br>
<a href="https://www.redhat.com/mailman/listinfo/feedhenry-raincatcher" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/feedhenry-raincatche<wbr>r</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
______________________________<wbr>_________________<br>
Feedhenry-raincatcher mailing list<br>
<a href="mailto:Feedhenry-raincatcher@redhat.com" target="_blank">Feedhenry-raincatcher@redhat.c<wbr>om</a><br>
<a href="https://www.redhat.com/mailman/listinfo/feedhenry-raincatcher" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/feedhenry-raincatche<wbr>r</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="m_6093741392744246570mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
Feedhenry-raincatcher mailing list
<a class="m_6093741392744246570moz-txt-link-abbreviated" href="mailto:Feedhenry-raincatcher@redhat.com" target="_blank">Feedhenry-raincatcher@redhat.<wbr>com</a>
<a class="m_6093741392744246570moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/feedhenry-raincatcher" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/feedhenry-<wbr>raincatcher</a>
</pre>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>