You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Ulrich Stärk <ul...@spielviel.de> on 2013/01/06 17:15:18 UTC
Re: Tapestry 5.4-alpha-2
Can we please stop using per-preview repositories and put previews into the snapshots repository
where they belong IMO? That would make those previews more easily available since the repository URL
won't have to be changed between snapshots.
Uli
On 03.01.2013 23:01, Howard Lewis Ship wrote:
> I've created a new preview release, available from the Maven repository at
>
> https://repository.apache.org/content/repositories/orgapachetapestry-096/
>
> this includes the new jQuery support I recently blogged about.
>
> Feedback desperately desired!
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Tapestry 5.4-alpha-2
Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
5.4-alpha-x should not be a snapshot at all.
It's a release. An alpha release, but a release.
5.4-SNAPSHOT should be the bleeding edge nightly builds.
On Jan 22, 2013, at 6:54 AM, Massimo Lusetti wrote:
> I feel lazy but now I think I understood what Uli was talking about.
>
> If you look at the apache snapshot repository, for example the IoC:
> https://repository.apache.org/content/groups/snapshots/org/apache/tapestry/tapestry-ioc/
>
> You can see that the latest snapshot is 5.4-alpha-3-SNAPSHOT instead of
> 5.4-SNAPSHOT
>
> I do agree that having a "frozen snapshot" like 5.4-alpha-3 is a very good
> idea for the early adopters but the latest snapshot has to remain
> 5.4-SNAPSHOT which is the real bleeding edge and used by T5 developers.
>
> So what Jenkins builds should go with 5.4-SNAPSHOT while if we want to
> produce an intermediate release for early adopters we should change it to
> 5.4-alpha-x or whatever applicable.
>
> Thoughts!?
>
>
> On Tue, Jan 8, 2013 at 12:40 AM, Massimo Lusetti <ml...@gmail.com> wrote:
>
>> I do agree, having the possibility to specify a precise target as a dep
>> while testing an upgrade is by far a better solution then having a moving
>> target
>>
>
>
>
> --
> Massimo
> http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Tapestry 5.4-alpha-2
Posted by Massimo Lusetti <ml...@gmail.com>.
I feel lazy but now I think I understood what Uli was talking about.
If you look at the apache snapshot repository, for example the IoC:
https://repository.apache.org/content/groups/snapshots/org/apache/tapestry/tapestry-ioc/
You can see that the latest snapshot is 5.4-alpha-3-SNAPSHOT instead of
5.4-SNAPSHOT
I do agree that having a "frozen snapshot" like 5.4-alpha-3 is a very good
idea for the early adopters but the latest snapshot has to remain
5.4-SNAPSHOT which is the real bleeding edge and used by T5 developers.
So what Jenkins builds should go with 5.4-SNAPSHOT while if we want to
produce an intermediate release for early adopters we should change it to
5.4-alpha-x or whatever applicable.
Thoughts!?
On Tue, Jan 8, 2013 at 12:40 AM, Massimo Lusetti <ml...@gmail.com> wrote:
> I do agree, having the possibility to specify a precise target as a dep
> while testing an upgrade is by far a better solution then having a moving
> target
>
--
Massimo
http://meridio.blogspot.com
Re: Tapestry 5.4-alpha-2
Posted by Massimo Lusetti <ml...@gmail.com>.
I do agree, having the possibility to specify a precise target as a dep
while testing an upgrade is by far a better solution then having a moving
target
Re: Tapestry 5.4-alpha-2
Posted by Kalle Korhonen <ka...@gmail.com>.
On Mon, Jan 7, 2013 at 1:49 AM, Ulrich Stärk <ul...@spielviel.de> wrote:
> On 07.01.2013 00:29, Howard Lewis Ship wrote:
> > Snapshots have their place, but the stability of a preview release has
> its
> > value, despite the hoops Nexus makes you jump through. It says that this
> > particular binary represents a consistent view, and is stable enough for
> > evaluation and discussion; a snapshot doesn't have even that level of
> > guarantee.
> What are preview builds other than a snapshot at a specific point of time?
> IMO snapshots, or nightly builds, also represent a consistent view: the
> build and all tests passed
> and for Tapestry with its numerous tests this probably means more than
> other projects' stable
> releases in terms of stability.
>
The difference is that it's frozen snapshot rather than a moving target.
It's difficult to sort out what issues there are in your own application
code if you can't control the other variables. Many organizations would
like to start testing against 5.4 so they can move to it when an actual
release is available. We use snapshots all the time but I never allow
snapshot dependencies to external libraries outside our organization; it
just doesn't make sense to me since they are not in my control and I
suspect this is the same way in many other organizations. Downloading the
preview releases from a temporary Maven repo may be an inconvenience but
really, it's far far better than having to download them manually then
check them into your source control. To me, it's pretty reasonable
compromise in between nightly builds and actual, sanctioned,
must-be-voted-on releases.
Kalle
Re: Tapestry 5.4-alpha-2
Posted by Ulrich Stärk <ul...@spielviel.de>.
On 07.01.2013 00:29, Howard Lewis Ship wrote:
> We had a big discussion some time agao about the way to do things, and we
> even captured the results of the dicussion in Confluence:
>
> http://tapestry.apache.org/version-numbers.html
>
> So for once, I feel like I'm on the right side of a "following procedures"
> discussion.
What you are quoting concerns version numbering only.
>
> Snapshots have their place, but the stability of a preview release has its
> value, despite the hoops Nexus makes you jump through. It says that this
> particular binary represents a consistent view, and is stable enough for
> evaluation and discussion; a snapshot doesn't have even that level of
> guarantee.
What are preview builds other than a snapshot at a specific point of time?
IMO snapshots, or nightly builds, also represent a consistent view: the build and all tests passed
and for Tapestry with its numerous tests this probably means more than other projects' stable
releases in terms of stability.
Anyway, my point is not about whether we should rename preview builds but solely were we make them
available to our users. I find the one maven repository per preview build inconvenient for our users
(and myself of course). Since they clearly don't belong into the main maven repo, the next best
thing would be to upload them to the snapshot repository.
I don't feel strongly about this, it's just something that crossed me when I had to update my maven
repository URLs and could not just simply change the Tapestry version number.
Uli
>
> I'm always up for more discussion and votes on procedure ... but I'd much
> rather see people putting their energy into code or documentation right now!
>
>
>
>
>
> On Sun, Jan 6, 2013 at 4:15 PM, Ulrich Stärk <ul...@spielviel.de> wrote:
>
>> Can we please stop using per-preview repositories and put previews into
>> the snapshots repository
>> where they belong IMO? That would make those previews more easily
>> available since the repository URL
>> won't have to be changed between snapshots.
>>
>> Uli
>>
>> On 03.01.2013 23:01, Howard Lewis Ship wrote:
>>> I've created a new preview release, available from the Maven repository
>> at
>>>
>>>
>> https://repository.apache.org/content/repositories/orgapachetapestry-096/
>>>
>>> this includes the new jQuery support I recently blogged about.
>>>
>>> Feedback desperately desired!
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Tapestry 5.4-alpha-2
Posted by Howard Lewis Ship <hl...@gmail.com>.
We had a big discussion some time agao about the way to do things, and we
even captured the results of the dicussion in Confluence:
http://tapestry.apache.org/version-numbers.html
So for once, I feel like I'm on the right side of a "following procedures"
discussion.
Snapshots have their place, but the stability of a preview release has its
value, despite the hoops Nexus makes you jump through. It says that this
particular binary represents a consistent view, and is stable enough for
evaluation and discussion; a snapshot doesn't have even that level of
guarantee.
I'm always up for more discussion and votes on procedure ... but I'd much
rather see people putting their energy into code or documentation right now!
On Sun, Jan 6, 2013 at 4:15 PM, Ulrich Stärk <ul...@spielviel.de> wrote:
> Can we please stop using per-preview repositories and put previews into
> the snapshots repository
> where they belong IMO? That would make those previews more easily
> available since the repository URL
> won't have to be changed between snapshots.
>
> Uli
>
> On 03.01.2013 23:01, Howard Lewis Ship wrote:
> > I've created a new preview release, available from the Maven repository
> at
> >
> >
> https://repository.apache.org/content/repositories/orgapachetapestry-096/
> >
> > this includes the new jQuery support I recently blogged about.
> >
> > Feedback desperately desired!
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com