--
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig
Tel.: +49-531-24330-0
Fax: +49-531-24330-99
http: www.bredex.de
Geschäftsführer: Andreas Vogel, Ulrich Obst, Achim Lörke
Amtsgericht Braunschweig HRB 2450
Hi Alex. It was the link to the content on the Bredex server that caught my attention.
It really can't be there if it's part of the open source project. Even if it is accessible to everybody, that it is on a server controlled by Bredex violates vendor neutrality and is a roadblock for participation by non-Bredex employees on the project.
Pointers to the blog entries are fine, but "Developer Manual" seems like a far more official document that at least sounds like it should be part of the project.
Wayne
Hi Wayne,
Thanks for your comment. Are you referring to the fact that Eric noticed that it wasn’t available for unregistered users? If so, I changed that, see:
https://dev.eclipse.org/mhonarc/lists/technology-pmc/msg06452.html
If you’re talking about the build process, all our docs are built as part of the Eclipse build:
https://hudson.eclipse.org/jubula/job/jubula-nightly/lastBuild/consoleFull
(search for
Building org.eclipse.jubula.client.ua.help)
If neither of those is what you meant, just let me know.
Tomorrow is a holiday in Germany, and Friday is a day off – so I’ll be able to reply to any other mails at the beginning of next week.
Best regards,
Alex
--
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig
Tel.: +49-531-24330-0
Fax: +49-531-24330-99
http:
www.bredex.de
Geschäftsführer: Andreas Vogel, Ulrich Obst, Achim Lörke
Amtsgericht Braunschweig HRB 2450
That access to the in-progress developer guide is restricted to employees of a single company is a red flag for me. Is there any reason why this can't be built using an open channel?
Wayne
On 11/05/15 11:50 AM, Eric Rizzo wrote:
Hi, Alex.
When I tried to view the Developer Manual from your New & Noteworthy page (https://www.eclipse.org/jubula/new.php), it takes me to a login screen on
http://testing.bredex.de/
- is that manual published anywhere on eclipse.org? I think it needs to be, correct?
Since this is the first version of the client API, I was curious to know if you've taken steps to make sure it's sufficiently stable for public release. For example, is some of the API marked as "provisional" as is typical with new APIs for other Eclipse projects
(to allow for some evolution)? Or perhaps you've taken other steps to ensure you won't face a dilemma of backwards-compatibility vs. necessary evolution in your next release?
Eric
Hello Technology PMC,
we kindly ask for the PMC’s approval of the 3.1.0 release of Jubula (as part of the Mars release). The release documentation is at
https://projects.eclipse.org/projects/technology.jubula/releases/3.1-mars/review
The IP Log will be sent off this week.
Thanks and best regards,
Alex
--
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig
Tel.: +49-531-24330-0
Fax: +49-531-24330-99
http: www.bredex.de
Geschäftsführer: Andreas Vogel, Ulrich Obst, Achim Lörke
Amtsgericht Braunschweig HRB 2450
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/technology-pmc
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/technology-pmc
