Hi
I was going over mantis to see what were the bugs and next actions I should integrate. So now I imagine that I should let the team/team leader work and they will produce new version of packages. Is it right?
Here is the list I collected Andreas: Compression, FFI, Graphics, Balloon
Goran: Network
Juan: Morphic
Cees: Files
Stef
Yes, that's the general idea. We fix bugs and when we're happy with a version, we drop it into the inbox.
Of course, only insofar as there are package teams...
On 10/28/05, stéphane ducasse ducasse@iam.unibe.ch wrote:
Hi
I was going over mantis to see what were the bugs and next actions I should integrate. So now I imagine that I should let the team/team leader work and they will produce new version of packages. Is it right?
Here is the list I collected Andreas: Compression, FFI, Graphics, Balloon
Goran: Network
Juan: Morphic
Cees: Files
Stef
Hi Stef,
My team should produce versions of: Morphic,MorphicExtras, Etoys, FlexibleVocabularies, Nebraska, StarSqueak. These are the main parts that the old big Morphic package was broken in.
BTW, is there anything written about how to publish new versions of a package? I would need some hints (i.e. url, userid, pwd). What happens if someone needs to modify a package he does not stweard? Are there restrictions on who can update what?
Thanks, Juan Vuletich ----- Original Message ----- From: "stéphane ducasse" ducasse@iam.unibe.ch To: "The general-purpose Squeak developers list" squeak-dev@lists.squeakfoundation.org Sent: Friday, October 28, 2005 3:55 PM Subject: About package responsible
Hi
I was going over mantis to see what were the bugs and next actions I should integrate. So now I imagine that I should let the team/team leader work and they will produce new version of packages. Is it right?
Here is the list I collected Andreas: Compression, FFI, Graphics, Balloon
Goran: Network
Juan: Morphic
Cees: Files
Stef
-- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.12.6/151 - Release Date: 10/28/2005
Hi!
Two important things:
1. If you are Team leader for a Steward team, register the package in SM. Please. Including PI name. Put it in "Official package in basic" or possibly "Official package in full". Yes, there may be other packages in those categories that don't really fit the bill - but that is a cleaning job. I think these categories should only hold stewarded packages.
2. When making changes that involve other stewarded packages - in Network we simply publish those modified MCs in our Network work repository (at source.squeakfoundation.org - if you don't have a repo of your own for "Morphic" yet. you should get one - Marcus and Doug can create new repos there - but I am unsure who else can do it) and clearly describe how they fit together in the version notes - and when we eventually push our new version of Network to the inbox at 3.9 we will explain what MCs belong together.
regards, Göran
"Juan Vuletich" jmvsqueak@uolsinectis.com.ar wrote:
Hi Stef,
My team should produce versions of: Morphic,MorphicExtras, Etoys, FlexibleVocabularies, Nebraska, StarSqueak. These are the main parts that the old big Morphic package was broken in.
BTW, is there anything written about how to publish new versions of a package? I would need some hints (i.e. url, userid, pwd). What happens if someone needs to modify a package he does not stweard? Are there restrictions on who can update what?
Thanks, Juan Vuletich ----- Original Message ----- From: "stéphane ducasse" ducasse@iam.unibe.ch To: "The general-purpose Squeak developers list" squeak-dev@lists.squeakfoundation.org Sent: Friday, October 28, 2005 3:55 PM Subject: About package responsible
Hi
I was going over mantis to see what were the bugs and next actions I should integrate. So now I imagine that I should let the team/team leader work and they will produce new version of packages. Is it right?
Here is the list I collected Andreas: Compression, FFI, Graphics, Balloon
Goran: Network
Juan: Morphic
Cees: Files
Stef
-- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.12.6/151 - Release Date: 10/28/2005
On 11/3/05, Juan Vuletich jmvsqueak@uolsinectis.com.ar wrote:
My team should produce versions of: Morphic,MorphicExtras, Etoys, FlexibleVocabularies, Nebraska, StarSqueak. These are the main parts that the old big Morphic package was broken in.
Ok - note that we've done a lot of work to these as part of the current toolbuilder/plusttools integration of 3.9a, so you might want to take a peek at the versions in the 39a repository.
BTW, is there anything written about how to publish new versions of a package? I would need some hints (i.e. url, userid, pwd). What happens if someone needs to modify a package he does not stweard? Are there restrictions on who can update what?
The "rules" are (quoted, because this is how I think it should work and most here seem to agree, but nothing final and official):
- You develop/maintain your packages in your own repository. Typically (preferrably) this is a project on source.squeakfoundation.org which is created on request (check the site who the admins are) and where, typically, the team leader is project admin. The use of source.squeakfoundation.org is recommended because it is not impossible that we'll extend the version of squeaksource running there to accommodate specific tasks for the teams/integrators model.
- When the team decides a version is ready for public consumption, the team publishes it in the inbox of source.squeakfoundation.org - everyone can write to that box. Dropping a note to the 3.9a maintainers is considered polite.
- The 3.9a maintainers try to load the package in their latest image. If it loads, the package gets moved to the 39a repository and the next batch of updates will contain it. If it doesn't load, you'll get a notification and you can re-try yourself and fix it.
(of course, where I write '3.9a' read 'the current alpha release')
For patches on released versions e.g. because of Mantis bug reports, it is still the old method with changesets sent by mail to the update stream maintainer (which is ...?). When 3.9 gets released, the procedure above will likely stay the same but the requirements will get more strict. Quite likely, the integration team will not just test for loadability, but also run all unit tests and require they're all green or something like that before accepting a package.
Hth,
Cees
squeak-dev@lists.squeakfoundation.org
-
Cees De Groot -
goran＠krampe.se -
Juan Vuletich -
stéphane ducasse