We should just use the Managed Release Initial Checkpoint for this, vs making projects duplicate effort. It has a high level description requirement designed with exactly this in mind.
Daniel On Wed, Mar 7, 2018 at 5:43 PM Abhijit Kumbhare <[email protected]> wrote: > On a related note, projects - please let us know your high level goals as > well. This would be needed to address the following question in the > OpenDaylight Goals for 2018: > > > - What are the most important features or other technical aspects of > OpenDaylight to be accomplished this year? > > > It would be great if this is in a concise in the form of 2-3 bullets. > Please especially restrict to high level features / aspects only - > either the ones which would be relevant on an OpenDaylight wide level or > significantly enhance your project or the usability of your project. > > For the sake of speed & simplicity- you can add just reply-all to this > thread. > > > On Mon, Mar 5, 2018 at 10:33 PM, Kit Lou <[email protected]> wrote: > >> Good point An! >> >> There is a value "NOT_Integrated (UnManaged)" also - maybe opflex can use >> this value for now? Thanks! >> >> Best Regards, >> Kit Lou >> >> On Mon, Mar 5, 2018 at 3:10 PM, An Ho <[email protected]> wrote: >> >>> Hi Kit, >>> >>> >>> >>> Should we have a field for Unmanaged projects in Oxygen that are not >>> part of the Common Karaf Distribution (i.e. OpFlex). >>> >>> >>> >>> Best Regards, >>> >>> An Ho >>> >>> >>> >>> *From:* [email protected] [mailto: >>> [email protected]] *On Behalf Of *Daniel Farrell >>> *Sent:* Monday, March 05, 2018 12:54 PM >>> *To:* Kit Lou <[email protected]> >>> *Cc:* Release <[email protected]> >>> *Subject:* Re: [release] [Action Request for Oxygen Projects] Report >>> Oxygen Project Details by 18:00 UTC March 8 >>> >>> >>> >>> Note that this will be used for marketing the Oxygen release, so please >>> do keep it very high level. One or two paragraphs, understandable by the >>> average person at ONS. Please be sure to highlight things that would be >>> interesting to external consumers, like LFN projects or users. >>> >>> >>> >>> Thanks, >>> >>> Daniel >>> >>> On Mon, Mar 5, 2018 at 2:50 PM Kit Lou <[email protected]> wrote: >>> >>> Hello Oxygen Projects, >>> >>> >>> >>> Based on the TWS call earlier today, we are asking for a high-level, >>> human-readable description of what each project did in the oxygen release. >>> This should be submitted as a Jira *Project Plan *issue against the TSC >>> project. This will be reused for external communication/marketing for the >>> release. Please create a new *Project Plan* issue in the *tsc* project >>> as follows: >>> >>> >>> >>> · Select your project in the *ODL Project* field >>> >>> · Select the Oxygen version value in the *ODL Release* field >>> >>> · Select the appropriate value in the *ODL_Participation* field: >>> SNAPSHOT_Integrated (Managed) or RELEASE_Integrated(Managed) **For most >>> projects, you should choose the first value. The second value only >>> applies to ODLParent and Yangtools for now* >>> >>> · Select the value Final in the *ODL_Checkpoint* field >>> >>> · In the *Summary* field, put something like: Project-X Oxygen Release >>> details >>> >>> · In the *Description* field, fill in the details of your >>> accomplishments >>> >>> Please refer to [1] as a template. We ask that you complete this action >>> no later than the start of the TSC meeting this week - 10 AM PST or 18:00 >>> UTC Thursday, March 8. Thanks! >>> >>> >>> >>> Best Regards, >>> >>> Kit Lou >>> >>> >>> >>> [1] https://jira.opendaylight.org/browse/TSC-7 >>> >>> >> >> _______________________________________________ >> release mailing list >> [email protected] >> https://lists.opendaylight.org/mailman/listinfo/release >> >> > _______________________________________________ > TSC mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/tsc >
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
