Thanks @ohadlevy for making this happen.
On Tue, Aug 9, 2016 at 9:29 AM, Tom McKay wrote:
> The katello project will be moved under foreman as a sub-project next
> week. If there are any concerns, please speak up before then. Thanks!
>
> On Thu, Aug 4, 2016 at 10:03 AM,
The katello project will be moved under foreman as a sub-project next week.
If there are any concerns, please speak up before then. Thanks!
On Thu, Aug 4, 2016 at 10:03 AM, Lukas Zapletal wrote:
> > You do realize that every other plugin except Katello is under the
> foreman
>
> You do realize that every other plugin except Katello is under the foreman
> project in redmine, correct?
I haven't realized that, sorry for the noise :-)
--
Later,
Lukas #lzap Zapletal
--
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To
On 08/03/2016 06:30 PM, Tom McKay wrote:
On Wed, Aug 3, 2016 at 10:26 AM, Lukas Zapletal > wrote:
> Is there a case for keeping katello separate any longer, or can we
combine?
Because it's a plugin? And plugins have its own release cadence,
Lzap,
You do realize that every other plugin except Katello is under the foreman
project in redmine, correct?
David
On Wed, Aug 3, 2016 at 10:26 AM, Lukas Zapletal wrote:
> > Is there a case for keeping katello separate any longer, or can we
> combine?
>
> Because it's a
On Wed, Aug 3, 2016 at 10:26 AM, Lukas Zapletal wrote:
> > Is there a case for keeping katello separate any longer, or can we
> combine?
>
> Because it's a plugin? And plugins have its own release cadence, own
> planning (Release versions, Target versions) and Categories. I
On Wed, Aug 3, 2016 at 4:26 PM, Lukas Zapletal wrote:
>> Is there a case for keeping katello separate any longer, or can we combine?
>
> Because it's a plugin? And plugins have its own release cadence, own
> planning (Release versions, Target versions) and Categories. I don't see
> For example, several dev teams are experimenting with redmine "versions"
> for their sprints[1]. I don't think that a single version can include
One more thing. This will pollute Target versions, I don't like this.
Can't we simply use Issue trackers for that? Redmine is quite good in
creating
> Is there a case for keeping katello separate any longer, or can we combine?
Because it's a plugin? And plugins have its own release cadence, own
planning (Release versions, Target versions) and Categories. I don't see
enough benefits of merging when I consider all the above.
I don't know, I
+1 to less separation of the two projects in our overhead organization of
issues/features.
Andrew Kofink
Software Engineering Intern
Red Hat Satellite 6
akof...@redhat.com
On Wed, Aug 3, 2016 at 4:08 AM, Marek Hulán wrote:
> +1 for moving into Foreman project subtree
>
> --
I think having everything under one tree makes sense. Long-term, the
goal is to turn
Katello to not feel like a separate project, but rather an extension.
+1
Of course I'm not aware of some possible consequences if there are any?
-- Ivan
On Tue, Aug 2, 2016 at 3:56 PM, Tom McKay
As we try to work towards better bugzilla and redmine component definitions
and relations, I keep finding myself wishing I could use redmine for both
foreman and katello issues together.
For example, several dev teams are experimenting with redmine "versions"
for their sprints[1]. I don't think
12 matches
Mail list logo