Good to see there is a +1 for merging.
Following things I would like "done" before releasing
1) Get Teensy to work nicely
2) fix for 325
3) board name- port-baut rate in project explorer (like the version
control tools do but I don't find how :-( )
4) complete #349
5) fix for 347
6) documentation (all your items)
7) testing
of which 1 is something I'd like for merging but I fear that won't work
out fully.
I have made a wiki page on the release process :-)
https://github.com/jantje/arduino-eclipse-plugin/wiki/The-release-process
more below
Op 16-1-2016 om 19:03 schreef Wim Jongman:
+1 for merging. When do you want to release and what is still pending for this release?I'm well endowed in ccm with several tools (f.i. clearcase clearquest, rtc) but I seem to have a problem with git terminology. So yes a demonstration would be great.
Since you can now see the beauty of branches, how about using git flow. I am happy to give anyone a short demonstration and some general background on git's internal structure (as far as i know it ;).
What are the things that still need to be done?
### Documentation.
* New and Noteworthy for this release
* How does the workflow change for someone that currently has a Arduino IDE installed?
* 3.0.0 FAQ
* Website changes?
### Fixes
* The long path problem
* Keeping hold of the installation path
* Moving the install_path application parameter to a java property?
On Fri, Jan 15, 2016 at 11:54 PM, Jan Baeyens <jan@xxxxxxxxxx <mailto:jan@xxxxxxxxxx>> wrote:
I'm not sure what you guys think about it but I feel it is about
time to push branch "big change" to the "master" branch.
I think we increased the user experience and the version is stable
enough to make it the nightly.
I propose to make a branch 2.4 -just before pushing big change to
master- just for sakes of history.
Best regards
Jantje
<a
href="https://www.freelists.org/list/eclipse-arduino-dev>eclipse-arduino-dev@xxxxxxxxxxxxx
<mailto:eclipse-arduino-dev@xxxxxxxxxxxxx></a>
