On Wed, 2015-10-07 at 11:40 +0530, Carsten Ziegeler wrote:
> Looking at the list, I think:
> 
> - adapter - nice to have but we can go with 2.1.4

Started release since an IT fails with 2.1.4

> - engine - we can go with 2.4.2

You did not rollback to the release, so I just did that in r1707256. If
you do want a new engine relesae, please let me know.

> - jsp taglib - not sure

The only meaningful change is reduction of code duplication with SLING
-4298. Rolled back to released version in r1707258.

> - sightly bundles - not sure

I think Radu wants to cut another Sightly release, but I'll let him
decide that.

> - jcr webdav and usermanager - not sure

WebDAV has a new IT added for the changes ( SLING-4825 ) so I will
start a release vote.

I forgot about the usermanager :-), it's crucial for this release so I
also started a release vote for it.

Additionally there's the logservice bundle at 1.0.5-SNAPSHOT, with
improvement SLING-4563 - Log start level number on STARTLEVEL CHANGED
event . I think it's nice enough to have so I'll start a release vote
for that as well.

Robert

> 
> Regards
> Carsten
> 
> Am 07.10.15 um 11:31 schrieb Carsten Ziegeler:
> > We have several of snapshot references in launchpad. What should we
> > do
> > with them? Revert to latest release, release them?
> > 
> > Regards
> > Carsten
> > 
> > Am 07.10.15 um 01:40 schrieb Robert Munteanu:
> > > Hi,
> > > 
> > > I've started gathering the tasks that we need to do to call Sling
> > > 8 'released'.
> > > 
> > >   https://issues.apache.org/jira/browse/SLING-5095
> > > 
> > > The idea is to list all issues as sub-tasks, and then possibly
> > > link
> > > the sub-tasks to the implementation jira issues.
> > > 
> > > So, if you have anything which you think _must_ get in Sling 8,
> > > please
> > > add subtasks to SLING-5095 and I will wait for them to be done
> > > before
> > > starting the release.
> > > 
> > > The current plan is to start the release vote early next week,
> > > but a
> > > couple of days of delay will not hurt.
> > > 
> > > Cheers,
> > > 
> > > Robert
> > > 
> > 
> > 
> 
> 

Reply via email to