Hi folks,
I'd like to propose a rails4 branch under the Foreman organization on Github. This would give better visibility to the rails4 effort as well as providing more people than solely Tom Caspy the authority to carry out merges or rebases in the future, say, if Tom happens to not be available.
In a similar vein, I would also like to push for a regular merge or rebase of Foreman/develop onto Foreman/rails4 so that we can keep our rails4 effort as up-to-date as possible. Currently, there is a potential blocker in Katello/rails4 authorization due to Foreman/rails4 being far behind Foreman/develop.
I've created a Redmine issue to track this request, linked below.
···
--
Adam Price
Software Engineer
Red Hat Inc., Raleigh
adprice at redhat dot com
http://github.com/komidore64
> Hi folks,
>
> I'd like to propose a rails4 branch under the Foreman organization on Github. This would give better visibility to the rails4 effort as well as providing more people than solely Tom Caspy the authority to carry out merges or rebases in the future, say, if Tom happens to not be available.
>
> In a similar vein, I would also like to push for a regular merge or rebase of Foreman/develop onto Foreman/rails4 so that we can keep our rails4 effort as up-to-date as possible. Currently, there is a potential blocker in Katello/rails4 authorization due to Foreman/rails4 being far behind Foreman/develop.
>
> I've created a Redmine issue to track this request, linked below.
>
> Support #11855: Please rebase or merge Foreman/develop into Foreman/rails4 on a regular schedule - Foreman
Sounds like a good idea. If this happens, could we change the
test_plugin_pull_request job to run tests against both develop and
rails4?
As an outsider to the effort, I feel like I really don't have any
insight into the process, yet rails 4 does affect me and every other
developer. Is there a wikipage with a schedule somewhere? Or info to
help us understand the transition and what we need to be concerned
about?
E.g. I just happened to see the stabby lambda PR. There's what, dozens
of other things like that we need to be aware of? It might be nice to
track this on the wiki page of the most important things we need to
know, or send out some recurring e-mails with summaries of what was done
so we can follow along in your painful journey in upgrading.
Plugin developers also have no idea what they need to do to make their
plugins accessible, so I think it'd be appropriate to provide some
guidance on
Plugins - Foreman.
···
On Thu, Sep 17, 2015 at 09:35:03AM -0400, Adam Price wrote:
–
Adam Price
Software Engineer
Red Hat Inc., Raleigh
adprice at redhat dot com
http://github.com/komidore64
–
You received this message because you are subscribed to the Google Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
