[Framework-Team] Tickets management

[Nathan Van Gheem]

IMO, but maybe not the right time to talk about it, we should shut down
trac and only use github...

On Fri, Nov 14, 2014 at 5:06 AM, Johannes Raggam <raggam-nl at adm.at> wrote:

> aha, ok! i'm fine with that too :)
>
>
> On Fri, 2014-11-14 at 11:19 +0100, Eric Bréhault wrote:
> > Oh, I didn't mean it would replace the dev.plone.org tickets, I just
> > propose to link them to the Github issue #184, so they will be listed
> > in the tasks with the existing ones (be careful: in Github, tasks are
> > not issues; tasks are just checkable items in a list, just like
> > "ByLine design" at the moment is a task, but it is not related to an
> > issue).
> >
> >
> > So I would just add tasks like that:
> > Ticket #20133 KeyError:
> > 'plone.resources.development' https://dev.plone.org/ticket/20133
> >
> >
> >
> > And we would only close that ticket in dev.plone.org once it is
> > actually closed, but the main point is that we get in a single place
> > all the current "things" (=tasks) to do for Plone 5 and which ones are
> > blockers for beta release.
> >
> > On Fri, Nov 14, 2014 at 11:11 AM, Johannes Raggam <raggam-nl at adm.at>
> > wrote:
> >         sounds great +1 +1,
> >         please close the tickets on dev.plone.org then.
> >
> >         On Fri, 2014-11-14 at 09:49 +0100, Eric Bréhault wrote:
> >         > Hello,
> >         >
> >         >
> >         > Just a question about how Plone 5 tickets are supposed to be
> >         managed:
> >         > - this issue
> >         https://github.com/plone/Products.CMFPlone/issues/184
> >         > lists 72 tasks to be reviewed or to be done for Plone 5
> >         > - dev.plone.org contains 37 non-closed tickets for Plone 5
> >         milestone
> >         >
> >
> https://dev.plone.org/query?status=assigned&status=confirmed&status=new&status=reopened&milestone=5.0&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&report=73&order=priority
> >         >
> >         >
> >         > Is it OK if I add the dev.plone.org tickets as tasks in the
> >         Github
> >         > issue #184? (some are already there, but some are missing).
> >         > Or do you think it is not useful ?
> >         >
> >         >
> >         > Then I imagine we can add a "BLOCKER" mention to all the
> >         tasks
> >         > considered as blockers for Plone 5 beta into this issue.
> >         >
> >         >
> >         > What do you think?
> >         > (maybe the FWT already has a prefered way to handle that,
> >         which I am
> >         > not aware of)
> >         >
> >         >
> >         >
> >         > Eric
> >         >
> >         >
> >         >
> >         >
> >
> >         > _______________________________________________
> >         > Framework-Team mailing list
> >         > Framework-Team at lists.plone.org
> >         >
> >         https://lists.plone.org/mailman/listinfo/plone-framework-team
> >
> >
> >         --
> >         programmatic  web development
> >         di(fh) johannes raggam / thet
> >         python plone zope development
> >         plone framework  team  member
> >         mail: office at programmatic.pro
> >         web:  http://programmatic.pro
> >               http://bluedynamics.com
> >
> >
> >
>
> --
> programmatic  web development
> di(fh) johannes raggam / thet
> python plone zope development
> plone framework  team  member
> mail: office at programmatic.pro
> web:  http://programmatic.pro
>       http://bluedynamics.com
>
>
> _______________________________________________
> Framework-Team mailing list
> Framework-Team at lists.plone.org
> https://lists.plone.org/mailman/listinfo/plone-framework-team
>
>


-- 
Nathan Van Gheem
Solutions Architect
Wildcard Corp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plone.org/pipermail/plone-framework-team/attachments/20141114/74d00508/attachment.html>