integrated server bundle proposal

Well, if Scooby is dependent on .3 and you come out with a
.2.8  
release or something.

Or if Cosmo starts (or stops) doing something that Scooby
relied on  
before Scooby can handle it.

On Feb 8, 2006, at 6:37 PM, Brian Moseley wrote:

> On 2/8/06, Lisa Dusseault <lisaosafoundation.org> wrote:
>
>> Not entirely sure this should be done every time. 
We should consider
>> it when a new Scooby or Cosmo release is made but
possibly not every
>> time.
>
> why would we not do it?
> _______________________________________________
> Scooby mailing list
> Scoobyosafoundation.org
> http://lists.osafoundation.org/cgi-bin/mailman/lis
tinfo/scooby

_______________________________________________
Cosmo mailing list
Cosmoosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo

On 2/8/06, Bobby Rullo <brosafoundation.org>
wrote:
> Well, if Scooby is dependent on .3 and you come out
with a .2.8
> release or something.

well that particular example is irrelevant, but sure, if
cosmo makes a
non-backwards-compatible change, then it doesn't make sense
to update
snarf until scooby has evolved to support the new change.

we control that manually though, by choosing not to change
the cosmo
dependency version in snarf's pom, so bear can fully
automate the
process of building snarf releases, eg: when a cosmo or
scooby release
happens, if snarf's pom has been updated to incorporate the
new
dependency, then make a new snarf release.
_______________________________________________
Cosmo mailing list
Cosmoosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo

To add my build/release point of view to the discussion ...

What Brian is proposing here fits my model of how the
distribution side 
will work.  The tinderbox setup will continuously build from
the source 
tree and upload a new bundle (or bundles) when it detects
any source 
changes.

The whole "who links to what and is dependent on
what" is controlled by 
changing the pom information as Brian describes.

As long as the bundle filename includes a version number
itself then we 
can ensure that older Cosmo/Scooby version match-ups are
saved/archived 
in the maven repository.

On Feb 8, 2006, at 7:00 PM, Brian Moseley wrote:

> On 2/8/06, Bobby Rullo <brosafoundation.org>
wrote:
>> Well, if Scooby is dependent on .3 and you come out
with a .2.8
>> release or something.
>
> well that particular example is irrelevant, but sure,
if cosmo makes a
> non-backwards-compatible change, then it doesn't make
sense to update
> snarf until scooby has evolved to support the new
change.
>
> we control that manually though, by choosing not to
change the cosmo
> dependency version in snarf's pom, so bear can fully
automate the
> process of building snarf releases, eg: when a cosmo or
scooby release
> happens, if snarf's pom has been updated to incorporate
the new
> dependency, then make a new snarf release.
> _______________________________________________
> Cosmo mailing list
> Cosmoosafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo
>
>
---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bearosafoundation.org
http://www.osafoundation
.org

bearcode-bear.com
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822
40B3 CD29


_______________________________________________
Cosmo mailing list
Cosmoosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo