Dear Eric,
I think having these instructions in the Wiki is a good idea, though I'd
rather have the keeping of the track of these in one place which shall
be our JIRA as the tasks can be similar from release to release, but not
the same. If you would like to put the progress in the page you co
Hi
Can this page[1] be a starting point? I will do the Javadoc part as I was
involved but I'm not sure to get all the other point. maybe linking them to the
jira.
Regards
Eric
[1]
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Branding
-Message d'origine-
De
Hi
Can this page[1] be a starting point? I will do the Javadoc part as I was
involved but I'm not sure to get all the other point
Regards
Eric
[1]
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Branding
Eric BARBONI | Research Assistant | T : 33.561.55.6964
ICS Team | IRI
Excellent, yes, would be great to note the difference as pointed out by Emi
for Mac OSX. Just go to the GitHub of the page and create a new pull
request after you've made a change, you'll see its super simple.
Awesome, great, the more doing this and getting their feet wet the better!
Gj
On Fri,
Yes, Tools > Options on Windows / Linux is moved to Preferences .
--emi
On Fri, Feb 8, 2019 at 5:01 PM Jeremy Cavanagh
wrote:
> Hi,
>
> Sadly, I am no Java expert so I don't feel I can make much of a
> contribution. However, I have seen the call for help with reviewing
> documentation. So, I s
Just see the subtasks of:
https://issues.apache.org/jira/browse/NETBEANS-2052
On 2/8/19 1:31 AM, Geertjan Wielenga wrote:
I volunteer to put in the splash screens once we have the branch. And this
time around we should really document everything we do, i.e., a release
check list -- e.g., new sp
Hi,
Sadly, I am no Java expert so I don't feel I can make much of a
contribution. However, I have seen the call for help with reviewing
documentation. So, I started by following the Java Tutorial. Almost
immediately I found a problem on the Code Completion page, specifically
customizing code
I volunteer to put in the splash screens once we have the branch. And this
time around we should really document everything we do, i.e., a release
check list -- e.g., new splash screens, change the About box, change the
titlebar, change the reference to the user/cache dir, etc, i.e., make a
list of
I know, that this could happen, but JIRA for Apache is a global tool where
everyone on the world can have access and create tickets. And the language is
and should be english. Maybe a better communication about it would be good.
Otherwise they thought there are people for each language to help.
