[katello-devel] Katello 1.3/1.4 Feature Planning

Eric D Helms ericdhelms at gmail.com
Fri Dec 7 13:45:54 UTC 2012


Two others that crossed my mind:

- Getting on the Rails 3.2 stack (to be congruent with Aeolus)
- Splitting up the codebase into focused repositories


On Thu, Dec 6, 2012 at 2:07 PM, Brad Buckingham <bbuckingham at redhat.com>wrote:

>  Another thought which might be nice... How about possibly a
> documentation day (or partial day)?  This could be for supporting many
> forms of documentation (blogs, user docs, manpages (if any needed),
> screencasts...).
>
> Brad
>
>
> On 12/06/2012 02:04 PM, Eric D Helms wrote:
>
> I think this would be a great time for a bug-day and am going to organize
> such.  Bug day being, whole team sitting down and pounding through the list
> of bugs to verify, ask for more information or try and fix.  I figure we
> can get a conference room for a day (in the U.S.) to allow easy discussion
> since inevitably some people have more information than others in some
> areas.
>
>  Team Other side of the Pond -- since the time zone difference is great
> enough, if you guys would also like to put together a bug day around the
> same time and if someone from your side would like to volunteer the
> organization of it that would be great.
>
>  - Eric
>
>
> On Thu, Dec 6, 2012 at 12:47 PM, Tom McKay <thomasmckay at redhat.com> wrote:
>
>>
>>
>> ----- Original Message -----
>> > From: "Eric D Helms" <ericdhelms at gmail.com>
>> > To: katello-devel at redhat.com
>> > Sent: Thursday, December 6, 2012 11:58:28 AM
>> > Subject: [katello-devel] Katello 1.3/1.4 Feature Planning
>> >
>> >
>>  > Howdy,
>> >
>> >
>> > As I prepare the Katello 1.2 release, I thought I would get the ball
>> > rolling on feature planning for Katello 1.3. As it stands, the focus
>> > of Katello 1.3 is Pulp V2 integration. However, a lot of other
>> > features and work will go on during now and when the Pulp V2 work is
>> > ready. So I'd like to get a rough idea of what features we plan to
>> > try and get into this next release and potentially any beyond that
>> > for the next release nanny to work from. Current rough time frame
>> > for Pulp V2 integration is late January, early February time frame
>> > and thus this release will be based on feature completion not a hard
>> > timed release.
>> >
>> >
>> > Katello 1.3 Features
>> > - Pulp V2 integration
>> > - Pulp V2 upgrades
>> >
>> >
>> >
>> >
>> > Katello 1.4 Features
>>  > _______________________________________________
>> > katello-devel mailing list
>> > katello-devel at redhat.com
>> > https://www.redhat.com/mailman/listinfo/katello-devel
>>
>>
>>  Reduction of the 564 open BZs. Seriously, if we're not going to fix them
>> let's just mass close.
>>
>>
>> https://bugzilla.redhat.com/buglist.cgi?quicksearch=NEW%2CASSIGNED%20product%3A%22katello%22%2C%22CloudForms%20System%20Engine%22%2C%22Subscription%20Asset%20Manager%22&list_id=912048
>>
>
>
>
> _______________________________________________
> katello-devel mailing listkatello-devel at redhat.comhttps://www.redhat.com/mailman/listinfo/katello-devel
>
>
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/katello-devel/attachments/20121207/a7768918/attachment.htm>


More information about the katello-devel mailing list