JDK 9 RFR of 8161402: Provide a javadoc description for java.prefs module
Lance Andersen
lance.andersen at oracle.com
Tue Jul 19 21:59:56 UTC 2016
OK, now I am confused :-)
Earlier in the thread, it was raised that it would be more efficient to have 1 bug and 1 owner. Your reply seemed to agree to that, but now it looks like you are rethinking this?
The module descriptions seemed to all be something similar to
The {@code java.XXX} module defines and exports the XXX API
At least that is what was being proposed on the thread for] Brian’s changeset
Best
Lance
> On Jul 19, 2016, at 5:52 PM, Alexandre (Shura) Iline <alexandre.iline at oracle.com> wrote:
>
> I was originally assuming that different engineers would be responsible for providing descriptions for different modules … if to merge all that into one bug, a single person will either have to come up with everything himself/herself or go around and ask for all the description in the e-mail. Should we instead create an umbrella issue which the sub-tasks suggesting descriptions in the comments or something similar?
>
> Shura
>
>> On Jul 19, 2016, at 2:43 PM, Lance Andersen <lance.andersen at oracle.com <mailto:lance.andersen at oracle.com>> wrote:
>>
>> Brian and I exchanged email off-line. I will take ownership of this and grab the existing bugs Wed.
>>
>> Best
>> Lance
>>> On Jul 19, 2016, at 11:31 AM, Brian Burkhalter <brian.burkhalter at oracle.com <mailto:brian.burkhalter at oracle.com>> wrote:
>>>
>>> On Jul 19, 2016, at 8:20 AM, Alexandre (Shura) Iline <alexandre.iline at oracle.com <mailto:alexandre.iline at oracle.com>> wrote:
>>>
>>>>> On Jul 19, 2016, at 8:19 AM, Alan Bateman <Alan.Bateman at oracle.com <mailto:Alan.Bateman at oracle.com>> wrote:
>>>>>
>>>>> I agree, I think we should close the bulk of these issues and replace with one issue.
>>>>>
>>>>> Shura - are you okay if we close all the issues that you created and replace them with one?
>>>>
>>>> Absolutely.
>>>
>>> If no one else wants to do it I can take this task of collapsing the issues, etc. It should comprise also reexamining the verbiage already in place (java.base, java.desktop, etc.).
>>>
>>> Brian
>>
>> <oracle_sig_logo.gif> <http://oracle.com/us/design/oracle-email-sig-198324.gif>
>> <http://oracle.com/us/design/oracle-email-sig-198324.gif> <http://oracle.com/us/design/oracle-email-sig-198324.gif>
>> <http://oracle.com/us/design/oracle-email-sig-198324.gif>Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037
>> Oracle Java Engineering
>> 1 Network Drive
>> Burlington, MA 01803
>> Lance.Andersen at oracle.com <mailto:Lance.Andersen at oracle.com>
>>
>>
>>
>
<http://oracle.com/us/design/oracle-email-sig-198324.gif>
<http://oracle.com/us/design/oracle-email-sig-198324.gif> <http://oracle.com/us/design/oracle-email-sig-198324.gif>
<http://oracle.com/us/design/oracle-email-sig-198324.gif>Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037
Oracle Java Engineering
1 Network Drive
Burlington, MA 01803
Lance.Andersen at oracle.com <mailto:Lance.Andersen at oracle.com>
More information about the core-libs-dev
mailing list