Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [dsdp-mtj-dev] Europa Simultaneous Release?
Title: Europa Simultaneous Release?
Hi!
 
As Kevin pointed out, there may be a lot of  things to do in our next release and therefore 
all additional work might be too much.
Probably we should keep this in our minds and try to participate to the 'Europa train' after we get the
1.0 release out.
 
-a

From: dsdp-mtj-dev-bounces@xxxxxxxxxxx [mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] On Behalf Of ext Gaff, Doug
Sent: 06 November, 2006 21:05
To: Mobile Tools for The Java Platform mailing list
Subject: RE: [dsdp-mtj-dev] Europa Simultaneous Release?

Hi MTJ developers,

 

I’m glad to see you discussing this.  I would like to encourage you to participate in Europa and get “on the train”.  The visibility for your project and technology will increase quite a bit if MTJ is in Europa.  Also, getting on the train now will make it easier for you to be part of future Eclipse train releases, since the process and requirements will likely be similar from release to release.

 

Regarding #9 and #10 in the required options: the choice is yours who you would like to represent the project.  The requirement for this representative is someone who knows the build and update mechanisms for MTJ.  This person will need to coordinate with others in the project to make sure the Europa builds and update site population happen at the right time.

 

Doug Gaff

DSDP PMC lead

 

 

From: dsdp-mtj-dev-bounces@xxxxxxxxxxx [mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] On Behalf Of Arto.Laurila@xxxxxxxxx
Sent: Monday, November 06, 2006 5:32 AM
To: dsdp-mtj-dev@xxxxxxxxxxx
Subject: RE: [dsdp-mtj-dev] Europa Simultaneous Release?

 

Hi all,

To get this started, I did include some opinions and our work estimates to follow the "Europa" simultaneous release process.

Any opinions are welcome ...

As these are required for participation:

  1. The projects must work together. 
    -> This means that MTJ has to make a lot more testcases for that.
    -> Work estimate 1 man month (must do also during our milestones (aka during builds) and before release)
  2. Projects must have build process maturity and their own functional project update site - the Europa site will reference these sites, not replace them. 
    -> We have to get an update site, our build process is quite ok.
    -> Work estimate 1 week (one or two days for creating and three or four for testing) 
  3. Projects must optimize their update site using pack200 to reduce bandwidth utilization and provide a better update experience for users. Additionally, they should do site digesting. 
    -> Also these we should include in our build process
    -> Work estimate 1 week 
  4. Projects must use 4-part version numbers. 
    -> Very small issue
    -> Work estimate 1 day
  5. Projects must provide both run-times and SDKs through their update sites and thence through the Europa update site. (The Planning Council identified that this might not be technically possible due to bugs in the update manager's computation of required dependencies. We will remove this requirement if it proves to be impossible.) 
    ->Already MTJ does this
    -> Work estimate 0 day 
  6. Projects must use signed plugins using the Eclipse certificate. 
    -> This we would need to do
    -> Work estimate 1 week  
  7. Any third-party plug-ins that are common between projects must be consumed via Orbit; the final Europa release will not have duplicate third-party libraries (note that this only applies to identical versions of the libraries; thus if project A requires foo.jar 1.6 and project B uses foo.jar 1.7, that's ok). 
    -> No problem to us
    -> Work estimate 0 day 
  8. All plug-ins must correctly list their required JVM versions in the manifest/plugin.xml. 
    -> Small issue for us
    -> Work estimate one or two days 
  9. Project representatives must attend the planning meetings and conference calls - you have to be involved to be involved. 
    -> Does this mean Rauno or Mika or the development guys?
  10. At least one person from each project must subscribe to cross-project bug inbox, i.e. edit Bugzilla prefs to watch cross-project.inbox@xxxxxxxxxxx 
    -> See above
  11. Build team members from each project will provide communication channels: phone, mail, IM, IRC and will be available during to-be-specified crucial integration times 
    -> No problem to us
    -> Work estimate 1 week
  12. Projects must have stated and demonstrated their intent to join Europa by the M4+0 date. Projects do so by adding themselves to the table/list above, along with their contact information. 
    -> Project management issue
  13. Projects that have demonstrated an inability to synchronize with Europa milestones by M6 will be removed from the Europa simultaneous release unless the remaining Europa projects vote to retain said project. 
    -> See above

And these are recommended for participating projects:

  1. Projects should have jar'ed plug-ins because this is good Eclipse citizenship. 
    ->OK MTJ already has nearly all as jarred, thus few plugins are as folders (but they do have some other content also) 
  2. Projects should use Eclipse message bundles, not Java bundles because this is a good Eclipse citizenship. (see Message Bundle Conversion Tool and [1]) 
    ->  We already have this. 
  3. Build reproducibility? Require that projects be buildable by community members. Should be identical bits (but not required). All build assets and documentation in CVS/Subversion. 
    -> This needs actually that the build process is documented.
    -> Work estimate one week 
  4. Non-project-team-members should be able to build each project. 
    ->See above
  5. Non-project-team-members should be able to run unit tests on each project. 
    -> See above
  6. Source tarballs should be created for Linux distros to build with. 
    -> This we should do also
    -> Work estimate 2 days 
  7. Should have new & noteworthy for each milestone. Should be something readable and usable not just a static list of all the bugs. Corollary: individual new & noteworthy should be linked in to the collective New & Noteworthy. 
    -> A small task for us. We should collect some information about the active tasks and put those in some txt file. 
  8. Projects should use ICU4J. 
    - Kevin, do you have an opinion for this?
  9. Projects should provide build RSS feeds as per the build workshop. 
    -> Rather small issue, but this I would not feel to be the most important now.
  10. Projects should have a written ramp down policy. (One of the issues identified with this guideline is that its not so much the ramp down policy of how many votes are needed for each bug fix that we need to be consistent on, but rather the meaning of each of the milestones and release candidates. Here [2] is the Platform 3.2 ramp down policy as a guideline for other projects.) 
    -> This needs some more discussion.

 

-Arto

From: dsdp-mtj-dev-bounces@xxxxxxxxxxx [mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx]
Sent: 06 November, 2006 08:57
To: dsdp-mtj-dev@xxxxxxxxxxx
Subject: [dsdp-mtj-dev] Europa Simultaneous Release?

Hi,

As many of you are aware of simultaneuos release cycle of certain projects, I would like to rise a discussion should MTJ be part of it.

Here is a link to project wiki: http://wiki.eclipse.org/index.php/Europa_Simultaneous_Release.
If we want to be part of it, there are plenty of requriements for the project. Please, feel free to comment the topic.

        Rauno

Back to the top