Open Stack

The site was brought down due some XSS vulnerability concern and the team
is working on it.

On Tuesday, February 28, 2017, Kunzmann, Gerald <kunzmann at docomolab-euro.com>
wrote:

> Dear Shamail,
>
> Has the URL of the tracker changed? I cannot access anymore [1].
>
> Best regards,
> Gerald
>
> -----Original Message-----
> From: Shamail Tahir [mailto:itzshamail at gmail.com <javascript:;>]
> Sent: Tuesday, January 3, 2017 9:32 AM
> To: product-wg at lists.openstack.org <javascript:;>; user-committee <
> user-committee at lists.openstack.org <javascript:;>>
> Subject: [Product] User Story Trackers for OpenStack Feature Tracker
> Announcement
>
> Hi everyone,
>
> The first version of the OpenStack Feature Tracker (formerly known as the
> User Story Tracker) is essentially complete now thanks to the amazing work
> done by Teresita, Viridiana and Marcela from Intel (along with help from
> Jimmy and Jeremy from the OpenStack Foundation)...  We would like to
> announce the availability of this tool more broadly (e.g. dev ML) but don't
> want to proceed with that step until we have actual user story trackers in
> place.  If you visit the Feature Tracker[1], you will notice that the
> trackers currently being used just contain dummy/test data.
>
> We believe the 'first impression' for the tool will be more powerful if
> done with actual tracker data.  I know we have a few user stories, namely
> the bare-metal service and rolling upgrades, that are probably ready for
> tracking.  I would like to ask if the user stories owners could create
> actual trackers and submit them to our repository?
>
> [1] http://featuretracker.openstack.org
>
> --
> Thanks,
> Shamail Tahir
> t: @ShamailXD
> tz: Eastern Time
>
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org <javascript:;>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20170228/e4e4fd18/attachment.html>