[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [birt-dev] Contributing to BIRT
|
Thanks, Sissi and Sue for the bugzilla links and
information regarding the current state of the trunk
build process.
Actually, I have visited the wiki link below and it
didn't provide enough information for me, that is why
I started this thread.
http://wiki.eclipse.org/index.php/BIRT/FAQ/Birt_Project
Specifically:
>Q: How can I contribute code to the BIRT Project?
>
>Eclipse has an extensive process for code
>contributions. (LINK) Briefly, start by completing
>the (NAME) form required for all code submitters.
>Then, follow the (STUFF) development process
>to first submit bugs & patches via Bugzilla.
It seems that (LINK), (NAME), (STUFF) needs to be
filled in?
>Q: How do I build BIRT?
>
>Complete instructions are available on the Build
page.
The Build page describes the steps to build a
particular version of BIRT from Eclipse IDE.
However, like what I previously described on my
earlier
posts, it lacks release engineering build and
regression test process from the trunk codeline which
I think it is vital information for any new comers to
the project. I understand from Sue that these issues
are currently at work.
Perhaps this wiki page needs to be updated?
Regards,
Yip Ng
--- Sue Lee <slee@xxxxxxxxxxx> wrote:
> Hi Yip Ng,
>
> Thank you for your attention to BIRT!
>
> Build team send daily build status report to
> birt-dev mailing list. You can find build and smoke
> test status in it. But our daily build isn't always
> on trunk code. It depends on the dev schedule. For
> example, when we near the 2.1.1 release, 2.1.1
> branch was created, we sent a message to birt-dev to
> inform contributors that 2.1.1 bugs should go to
> 2.1.1 branch and 2.2.0 bugs should go to the trunk.
> BIRT daily build switched 2.1.1 branch until 2.1.1
> release. After 2.1.1 release, BIRT daily build go
> back to trunk code.
>
> Now top-level build scripts aren't available in CVS.
> And there isn't a Wiki page about the whole build
> process. So BIRT build system isn't open enough now.
> But we are working hard on it. We plan to switch to
> PDE build during 2.2.0 following Eclipse convention
>
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=150596),
> and the new build system will be available in CVS.
> We also plan to provide BIRT build process document
> in Wiki page
>
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=158493).
>
> Thanks,
>
> Sue Lee
>
> Actuate Corporation - Shanghai R&D Center
> Phone: (86)21-58826388
> Email: slee@xxxxxxxxxxx
>
>
> -----Original Message-----
> From: birt-dev-bounces@xxxxxxxxxxx
> [mailto:birt-dev-bounces@xxxxxxxxxxx] On Behalf Of
> Sissi Zhu
> Sent: 2006Äê10ÔÂ12ÈÕ 13:39
> To: Yip Ng; birt-dev@xxxxxxxxxxx
> Subject: RE: [birt-dev] Contributing to BIRT
>
> Hi Yip Ng,
>
> Thank you for your pay attention to BIRT project.
> There are still lots of work we are not doing so
> well, for example, there is no open instruction on
> how to contribute to BIRT project for outsiders, and
> how to make sure their codes will not break the BIRT
> build, etc. We will put more effort on this field
> and make the work more open for outside developers
> in the near future.
>
> As for the BIRT regression testing you mentioned, I
> think it something likes Junit testing. Every
> plug-in has its test folder in it that contains
> Junit test cases. Every check-in should make sure
> all the Junit test cases are passed before check the
> code into the CVS.
>
> For the build issue, Sue will give you a reply.
>
> Thanks,
>
> Sissi Zhu
>
> Actuate Software (Shanghai)
>
> Phone: (86)21-58826388 ext. 270
>
> http://www.actuate.com
>
> -----Original Message-----
> From: birt-dev-bounces@xxxxxxxxxxx
> [mailto:birt-dev-bounces@xxxxxxxxxxx] On Behalf Of
> Yip Ng
> Sent: 2006Äê10ÔÂ12ÈÕ 4:01
> To: birt-dev@xxxxxxxxxxx
> Subject: [birt-dev] Contributing to BIRT
>
> Sorry for cross posting this thread, I was informed
> that this list is more active than others and since
> this topic applies to all BIRT dev list in general,
> so
> I thought I'll post it here to get feedback from the
> BIRT community as well.
>
> --- Jane Tatchell <jtatchell@xxxxxxxxxxx> wrote:
> > > 1) I can't answer this one!
> >
> It would be indeed very helpful to have
> instructions
> on BIRT regression testing procedures available on
> BIRT Wiki or FAQ site, this would benefit new
> comers
> who wants to contribute to the BIRT community as
> this allows contributors to perform regression
> validation on a given set of test suite.
>
> > > 2) Most of the developers who contribute
> actively
> > to
> > > BIRT work in
> > > Shanghai and they all had a vacation last week.
> > > That's why you saw no
> > > activity. The most active list is the birt-dev
> > list.
> >
>
> I apologize for not being clear on what I meant by
> "active". I do see postings in birt-dev frequently
> but they are mostly mails from Bugzilla entries or
> code check-ins. I was hoping to find more open
> discussions on BIRT internals, design decisions,
> code reviews or even posts regarding changes to the
> trunk line that will affect the build, etc.
>
> I cannot seem to find these information in birt-dev
> or birt-report-engine-dev mail list. I think these
> sort of discussions would also benefit to the
> project
> as it opens up knowledge of the BIRT internals to
> new
> comers.
>
>
> Regards,
> Yip Ng
>
>
> > > -----Original Message-----
> > > From: birt-report-engine-dev-bounces@xxxxxxxxxxx
> > >
> >
> [mailto:birt-report-engine-dev-bounces@xxxxxxxxxxx]
> > > On Behalf Of Yip Ng
> > > Sent: Tuesday, October 10, 2006 4:32 PM
> > > To: birt-report-engine-dev@xxxxxxxxxxx
> > > Subject: [birt-report-engine-dev] Contributing
> to
> > > BIRT
> > >
> > > Hi, I am interested in contributing to the BIRT
> > > project. I have read
> > > through the BIRT's Wiki and FAQ site and I feel
> > that
> > > there seems to be
> > > some essential information missing for new
> comers.
> >
> > > For example:
> > >
> > > 1) The wiki explains how to build BIRT from CVS
> > with
> > > one of its version,
> > > but what about the testing process? If one
> makes
> > a
> > > change to BIRT
> > > internal, what test suite do one run in order to
> > > validate no regression
> > > is introduced in the BIRT designer, report
> engine,
> > > etc.? Some
> > > instructions
> > > here would be very helpful.
> > >
> > > 2) When I browse through birt-report-engine-dev
> or
> > > birt-dev mail list, I
> > > cannot seem to find open discussions regarding
> > > BIRT's internals, design
> > > decisions, etc. The list is not as active as I
> > > would expect for a dev
> > > list. Is there another channel where this is
> > > communicated? If so,
> > > please direct me to the correct channel.
> > >
> > > 3) Is there a daily build/test report on the
> > status
> > > of the trunk build?
> > >
> > >
> > >
> > > Regards,
> > > Yip Ng
> > >
> > >
> > >
> __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam? Yahoo! Mail has the best spam
> > > protection around
> > > http://mail.yahoo.com
> > > _______________________________________________
> > > birt-report-engine-dev mailing list
> > > birt-report-engine-dev@xxxxxxxxxxx
> > >
> >
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
