v.1 -> v.2.2, next rolling release, SFX-8 as main branch, demos
10 views
Skip to first unread message
Jarek Sacha
unread,
Jun 7, 2014, 11:38:28 PM6/7/14
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to scala...@googlegroups.com
There are a couple of things, kind of related:
v.1 seems to confuse some new users with JavaFX 1. We should
change it to follow JavaFX version, so for the next release we
will have something like v.2.2.60-R9, and refer to it shortly as
`SFX-2` (please comment on Issue #135)
It is 3 months since last release. The code now settled down
at GitHub. It is time to make rolling release with changes that
accumulated. I am planing to do it next Friday afternoon.
It is time to move the main development branch to `SFX-8`.
Looks that most
of the users are using SFX-8 already. I think we should
switch main branch just after the next release. Though I am
strangling a bit how to effectively do it. The current plan is
to branch the current `master` as `SFX-2`, then merge `SFX-8`
into `master` (actually override the `master` with `SFX-8`).
Though this does not look very clean as we will have dandling
`SFX-8` branch and a strange merge into `master`. Other option
may be to just rename `master` to `SFX-2` and `SFX-8` to
`master`. Thoughts? Suggestions how to move the main development
branch in the cleanest way? (please comment on Issue
#136)
Cleaning of scalafx-demos. Over time the demos project become
kind of messy. Some important demos, like ColorfulCircles in
SFX-8, no longer work. Many kind of obsolete or use outdated
API. Organization is kind of chaotic. We will need brief
description with screenshots of the demos on ScalaFX home page.
Anybody would like to tackle this? At least untangle this a bit?