Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jwt-dev] Next steps 
Hi Marc,
I thought that using the Update site would always provide the newest available version, thus 1.0.0 once we publish it, but I'm not sure, I may be wrong. Concerning the error message due to missing confs: I've change the value in "cmStatus.setCreateIfDoesntExist" from false to true which fixes the problem ;) Is this ok for you or are there maybe some bad side effects? Without this setting, there is always an error dialog displayed right after creation and each time when opening a workflow file.
I've also updated the converter and the integration build is currently running. If there aren't any other open issues we could release 1.0.0 by tomorrow I guess :) 

Best Regards,
Chris

Am 25.06.2010 19:23, schrieb Marc Dutoo:

Hi Chris, Florian

Sorry, I've been sick & busy at the same time this week ;_;

Nice note on the website Chris, and I agree with those steps.

Just one thing : the converter & conf model not created bug is in
Helios, which will probably be fare more used, so I'm not sure if it's
useful to patch it beforehand ? Especially as Anne said that Helios *is*
JWT 1.0 for all purposes...

Regards,
Marc

Christian Saad a écrit :

Hi Florian,

you're right, it should be done quickly. I've tagged 0.7.0 for Helios
on the CVS and updated the version tags to 1.0.0. Currently, the
converter is giving me a bit of trouble and also I'd like to fix the
bug which sometimes causes no conf model to be created and an error
message displayed because this can confuse users right from the start.
With the help of your ideas (thanks!!), I've made a short list of the
open points:

Must be done before releasing 1.0.0:

* Fix converter & conf model not created bug
* Move update site to SOA (http://download.eclipse.org/soa/jwt/
instead of http://download.eclipse.org/technology/jwt/)
* Update cbi-builder & Hudson job and promote to update site
* Prepare press release

Can be done shortly afterwards:

* Move bugzilla to SOA and bugs to 1.1.0 (check bugs for priority and
if they're still an issue)
* Move CVS to SOA (CVS/SVN) and update cbi-builder to reflect this
* Update entries in wiki (technology->SOA, cvs paths, version references)
* Update project plan according to bugs&mailing list requests
* Put message about 1.0.0 on HP and everywhere else
* Prepare AgilPro release (1.0.0, 2.0.0?)
* It's been a while since our last telco. Maybe we could set one up to
discuss short time (1.1.0, ESE) and long time plans

Best Regards and a nice weekend to you too :)
Chris

Am 25.06.2010 16:25, schrieb Florian Lautenbacher:

Hi Chris,

Thanks for adding a note to the website. I guess since the graduation
has
already been accepted together with the Helios release, we should try to
publish the release very quick. If we have an update on the update site,
could you please send another short email around? Then I'll also blog
about
it.

Concerning the next steps: what is left to be done to move to SOA TLP?
I guess there could be more things we should attempt for release 1.1?
Probably by now (with release 1.0) our roadmap is out of date, so we
should
start by defining our next steps in the roadmap first (including the
metamodel changes), not only concerning release 1.1, but also 1.2.
and 1.3.

Here, we should have a look at all requirements already in Bugzilla
and name
further requirements that we see and we would like to integrate, so
we can
prioritize them, order them to releases and also define the future
release
dates that will come next (probably following the release time of
about 6
months that we currently have).

In order for that, we should ask *everybody* following jwt-dev to let us
know their future attempts, plans and issues for JWT and probably we
should
have a telco in the next weeks to discuss about the roadmap.
(and we should also discuss about the ESE proposals we would like to
write;
alas, I didn't find a lot of time yet...).

Probably, we should send another email around which the readers of
jwt-dev
will more likely read than my long text here ;-) and which clearly
asks for
input.

Best regards and have a nice weekend,

Florian


-----Ursprüngliche Nachricht-----
Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Christian Saad
Gesendet: Donnerstag, 24. Juni 2010 18:02
An: Java Workflow Toolbox
Betreff: [jwt-dev] Next steps

Hi all,

now that Helios is released (I've added a quick note on the JWT page)
it's time to think about the next steps. As mentioned, we should quickly
go about the 1.0 release.

I'll try to prepare the update site by tomorrow from the current
codebase, i.e. the 0.7 release with several bugfixes (changing 0.7 to
1.0, technology to soa) if that's ok for you. Then we can go public :)

Afterwards, our next steps will probably include: Finish move to SOA
TLP, refactor meta model according to the discussed changes (1.1?).

Regards,
Chris
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev


_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev

_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev

_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev

Back to the top